MVSFORUMS.com

dharmaraju · Posted: Wed Jun 18, 2003 10:56 pm Post subject: when dataset edited

I am facing a peculiar problem. For the input file in my job, i copied production data and ran the job. It ran successfully. After that , i edited the input file and ran the same job, but itz timing out after a long time. Folks plz throw light on it
_________________
Arigato Guzaimasu ( Thank you in Japanese)
Dharmaraj

satjag · Beginner Joined: 19 Dec 2002 Posts: 19 Topics: 2

Hello,

More information is required for anlaysing this problem.

Upfront, what you can try probably is to reduce the number of records in your input file and try submitting the job.If that runs through, then you can double check the data you have edited.

As I said, more info is reqd .
_________________
Regards,
satjag

dharmaraju · Posted: Thu Jun 19, 2003 2:02 am Post subject:

ok its goes like this;
I copied the production data to my input file (only 50 records)
When i ran the job it was successful.
For the testing purpose, I edited only one record in the input file and again submited the job. But surprisingly it is hell lot of time and also timing out.
Again I copied the production data freshly and ran the job and it is succssful.
I am wondering why it is happening when i edit the data, that too adding a single character to the existing data
_________________
Arigato Guzaimasu ( Thank you in Japanese)
Dharmaraj

Dibakar · Posted: Thu Jun 19, 2003 4:37 am Post subject:

Don't you get some message with time outs, like waiting for dataset etc ...

dharmaraju · Posted: Thu Jun 19, 2003 6:37 am Post subject:

No, i am not getting any such message, even error messages of the program
_________________
Arigato Guzaimasu ( Thank you in Japanese)
Dharmaraj

satjag · Beginner Joined: 19 Dec 2002 Posts: 19 Topics: 2

Hello ,

Cannot really think why this is happening..

do you have xpediter in your shop ? Since input file has only fifty records,it would be of help if you can run through the xpediter and see the results.
_________________
Regards,
satjag

dharmaraju · Posted: Thu Jun 19, 2003 8:08 am Post subject:

Ok, is there any way to know the cause, like analysing the spool dump etc.,
_________________
Arigato Guzaimasu ( Thank you in Japanese)
Dharmaraj

slade · Posted: Thu Jun 19, 2003 3:46 pm Post subject:

Hi Dharmaraj,

In researching the history of COBOL debugging tools I found that the 1st was the eyeball, quickly followed by the DISPLAY stmt. Very Happy

If you don't have any debug tools or you can't spare the time to learn to use them,
I would extract the record you changed and no more than 1 or 2 other recs and use that as your I/P file. I find this trick keeps me from getting distracted and/or confused.

Then modify your pgm to put a DISPLAY at the top of your major processing loop. Put one as the 1st stmt in the pgm too. This will prove that you got to the part of the pgm that you wrote. I always prefix the DISPLAY text with "DEBUG~". Then when I need to get rid of them I just "x all debug~;del all x.

I suspect the edit of the rec is causing your pgm to loop. Execute the pgm w/the DISPLAY against the 3-4 rec file. Once you are sure it began execution cancel it immediately. Check the DISPLAY o/p and proceed from there. Add more displays, etc.

Regards, Jack.

dharmaraju · Posted: Fri Jun 20, 2003 12:33 am Post subject:

Hi.
You know in my previous shops, sometimes whenever i edited my input file and submitted job i was getting the 'dataset waiting error'. so i used to logout from the tso and delete the ISPF log. When I logback and submit the job again, it was a succes.. So here also, i was thinking of any such kind of unusual thing.
But in my situation, i was expecting some abend to occur(even in case of looping)
_________________
Arigato Guzaimasu ( Thank you in Japanese)
Dharmaraj

dorkhead · Posted: Wed Jun 25, 2003 4:34 am Post subject:

here is my stupid question (hope u'll excuse me ) did u leave the dataset ?

I mean exit form the dataset.
_________________
Dorkhead