262 value returned from dsjob -run

A forum for discussing DataStage<sup>®</sup> basics. If you're not sure where your question goes, start here.

Moderators: chulett, rschirm, roy

Post Reply
oracle
Participant
Posts: 43
Joined: Sat Jun 25, 2005 11:52 pm

262 value returned from dsjob -run

Post by oracle »

Hi -

Designed to run datastge job with TWS scheduler.
Some times during the scheduled runs our TWS jobs were getting failed with 262 error code but the actual job never gets triggered.

below is the TWS log

Code: Select all

+ /fsiis_h4/IBM/InformationServer/Server/DSEngine/bin/dsjob -run -mode NORMAL -jobstatus -param pxx=xx  env_xxx <dsseq name>
+ 1>> /dev/null 2>& 1
+ RETURNCODE=262
+ [[ 262 == 1 ]]
+ [[ 262 == 2 ]]
+ echo 'Datastage Failed.. Please check the Director Log...'
Datastage Failed.. Please check the Director Log...
+ exit 1
Any one experienced similar issue in the past ? Please guide
PaulVL
Premium Member
Premium Member
Posts: 1315
Joined: Fri Dec 17, 2010 4:36 pm

Post by PaulVL »

I recommend contacting your highly trained team of DataStage Administrators. You might also want to contact other teams to see if they have had the same experience.

Look at your TWS logs to see what your shell scripts are doing because your TWS flow calls a wrapper script that then calls DataStage.

Are you 100% sure your job didn't run?

Add timestamps to your script to see at what point you kick off the DS job, then at what point you exit it. You can then line up those times to see if DS kicked you a return code and it was still running. (that happens)

How much other stuff are you and your team running at the same time?
oracle
Participant
Posts: 43
Joined: Sat Jun 25, 2005 11:52 pm

Post by oracle »

Thanks for response Paul ..

TWS scheduler invokes wrapper script ...and this wrapper script mostly does nothing other than calling DataStage.We are experiencing this since almost few months and I am 100% sure that datastage job never gets triggered when we found this 262 return/error code.

At a single point of time we are invoking 50 datastage jobs with TWS scheduler which are running mostly with out any issues but some times randomly we are experiencing this 262 error/return code.

We have a shared server.. which might be causing this issue...but we have monitored cpu utilization while the jobs get failed , the batch user memory consumption and number of jobs running and found no issues with that.


We reached out to our Admin team ..but they are saying it is NOT a Datastage issue.

Clueless what is happening as I am unable to find any documentation on this issue.
PaulVL
Premium Member
Premium Member
Posts: 1315
Joined: Fri Dec 17, 2010 4:36 pm

Post by PaulVL »

Did you reach out to other teams yet?

An "intermittent" error like this is often attributed to consuming to many resources on the host in question. A lot of moving parts when you have TWS, shell scripts, DataStage, etc...

You are most likely not encountering the issue in your lower levels because you are not running the same volume of jobs in terms of concurrency and quantity of data. That "shared host" aspect is also going to bite you a bit. You never know what the other folks are doing.

Is your wrapper script Perl or Shell script?

Your admin team is sometimes lead by a highly charismatic individual who simply relies on his good looks alone to get by. I suspect that is the case with your setup.

The 50 jobs at a time, can be an issue depending on what you are doing too. Those others on the box might not be playing by the same rules as your team.

IE... they might not be using TWS. They might have a very heavy presence on the Head Node rather than on the Compute Nodes.
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Have you contacted support to see under what circumstances they think that a jobstatus value of 262 is possible? AFAIK, they only go up to 99. :?
-craig

"You can never have too many knives" -- Logan Nine Fingers
qt_ky
Premium Member
Premium Member
Posts: 2895
Joined: Wed Aug 03, 2011 6:16 am
Location: USA

Post by qt_ky »

I did some searching and did not find any error 262 in any DataStage documentation, header files, or support sites. I would therefore assume that the error code is not generated by DataStage.
Choose a job you love, and you will never have to work a day in your life. - Confucius
FranklinE
Premium Member
Premium Member
Posts: 739
Joined: Tue Nov 25, 2008 2:19 pm
Location: Malvern, PA

Post by FranklinE »

Assuming TWS is Tivoli Workload Scheduler...

https://www.ibm.com/support/knowledgece ... smsmst.pdf

AWSBIS262E No argument was supplied with -r.

AWSITA262E The user cannot launch this job because he does not have the required permissions.
Explanation: >The user does not have the required permission to run the job.
System action: The job does not run.
Operator response: Modify the permissions of the file to allow the user to launch it.

AWSJIM262E The field "{0}" contains an invalid
character as the first character.
User response: Enter the field without specifying an
invalid character as the first character.

EQQM262E YOU DO NOT HAVE AUTHORITY TO
USE THE EXECUTE COMMAND
Explanation: To use the function you selected, you
must have update authority to the EXECUTE resource.
System action: The request is rejected and the system
waits for you to respond.
User response: Contact your security administrator if
you need to use the EXECUTE command.
Franklin Evans
"Shared pain is lessened, shared joy increased. Thus do we refute entropy." -- Spider Robinson

Using mainframe data FAQ: viewtopic.php?t=143596 Using CFF FAQ: viewtopic.php?t=157872
oracle
Participant
Posts: 43
Joined: Sat Jun 25, 2005 11:52 pm

Post by oracle »

Thanks to all the experts for your wonderful insights ..I will keep you posted with the updates...Still we are working with DS Admins and we are planned to reach out to TWS Admins too
Post Reply