Error with dsjob command

Archive of postings to DataStageUsers@Oliver.com. This forum intended only as a reference and cannot be posted to.

Moderators: chulett, rschirm

Locked
admin
Posts: 8720
Joined: Sun Jan 12, 2003 11:26 pm

Error with dsjob command

Post by admin »

Were running into intermittent failures when running dsjob -jobinfo on UNIX.

The error message is:

ERROR: Failed to open project

Status code = 39202

Has anyone come across this before ?


regards,
Peter


NOTICE
This e-mail and any attachments are confidential and may contain copyright material of Macquarie Bank or third parties. If you are not the intended recipient of this email you should not read, print, re-transmit, store or act in reliance on this e-mail or any attachments, and should destroy all copies of them. Macquarie Bank does not guarantee the integrity of any emails or any attached files. The views or opinions expressed are the authors own and may not reflect the views or opinions of Macquarie Bank.
admin
Posts: 8720
Joined: Sun Jan 12, 2003 11:26 pm

Post by admin »

We encountered this error message when we exceeded the max processes / user, called maxuproc (AIX). The dsjob command creates connection processes that do not immediately end. This seemed to cause a "build up" of the process count. We were using dsjob within shell scripts to run the DataStage jobs, get job information, start/end log numbers, log messages, etc.

When we reduced our usage of "dsjob", the process count was greatly reduced. You can also ask your Unix admin to raise the setting for maxuproc.

fyi,

Doug

-----Original Message-----
From: Peter Oates [mailto:Peter.Oates@macquarie.com]
Sent: Monday, March 04, 2002 7:32 PM
To: datastage-users@oliver.com
Subject: Error with dsjob command


Were running into intermittent failures when running dsjob -jobinfo on UNIX.

The error message is:

ERROR: Failed to open project

Status code = 39202

Has anyone come across this before ?


regards,
Peter


NOTICE
This e-mail and any attachments are confidential and may contain copyright material of Macquarie Bank or third parties. If you are not the intended recipient of this email you should not read, print, re-transmit, store or act in reliance on this e-mail or any attachments, and should destroy all copies of them. Macquarie Bank does not guarantee the integrity of any emails or any attached files. The views or opinions expressed are the authors own and may not reflect the views or opinions of Macquarie Bank.
admin
Posts: 8720
Joined: Sun Jan 12, 2003 11:26 pm

Post by admin »

Doug,
The maxuprc for our servers is 29995 and even after we reduced our use of dsjob it still occurs but only on a dsjob -jobinfo command.

Peter

-----Original Message-----
From: Hall, Doug [mailto:Doug.Hall@anheuser-busch.com]
Sent: Wednesday, 6 March 2002 3:06 AM
To: datastage-users@oliver.com
Subject: RE: Error with dsjob command



We encountered this error message when we exceeded the max processes / user, called maxuproc (AIX). The dsjob command creates connection processes that do not immediately end. This seemed to cause a "build up" of the process count. We were using dsjob within shell scripts to run the DataStage jobs, get job information, start/end log numbers, log messages, etc.

When we reduced our usage of "dsjob", the process count was greatly reduced. You can also ask your Unix admin to raise the setting for maxuproc.

fyi,

Doug

-----Original Message-----
From: Peter Oates [mailto:Peter.Oates@macquarie.com]
Sent: Monday, March 04, 2002 7:32 PM
To: datastage-users@oliver.com
Subject: Error with dsjob command


Were running into intermittent failures when running dsjob -jobinfo on UNIX.

The error message is:

ERROR: Failed to open project

Status code = 39202

Has anyone come across this before ?


regards,
Peter


NOTICE
This e-mail and any attachments are confidential and may contain copyright material of Macquarie Bank or third parties. If you are not the intended recipient of this email you should not read, print, re-transmit, store or act in reliance on this e-mail or any attachments, and should destroy all copies of them. Macquarie Bank does not guarantee the integrity of any emails or any attached files. The views or opinions expressed are the authors own and may not reflect the views or opinions of Macquarie Bank.
Locked