IBM Mainframe Forum

Robert Sample wrote:Your FIRST problem is that an S322 is NOT a timeout (which would be an S522). S322 indicates that your job ran -- and was NOT waiting for a migrated data set recall -- and used all of the allowed CPU time (TCB). So your SECOND problem is to figure out whehter you've got a loop in your code or if the task you are running requires additional time to complete -- in which you need to work with your site support group, coworkers, or team leader to determine which job class to run in. Job classes tend to be limited by each site so only someone working AT YOUR SITE could tell you why the job class you used is limited and which job class you should be using for your job.

In other words, you completely misunderstand your problem and are looking at migrated data set recall when migrated data set recall has ABSOLUTELY nothing to do with your problem.

322

Explanation: One of the following occurred:

The system took a longer time to run a job, job step, or procedure than the time specified in one of the following:

The TIME parameter of the EXEC or JOB statement

The standard time limit specified in the job entry subsystem

For a started task under the master subsystem, the TIME parameter was not specified on the PROC statement of the catalogued procedure, and the PPT entry did not indicate a system task

System Action: The system abnormally ends the job, job step, or procedure.

Application Programmer Response: If the TIME parameter was not specified on the PROC statement of the catalogued procedure, add the TIME parameter or add a PPT entry for the PGM parameter. Otherwise, check for program errors. If none exist, specify a longer time in the TIME parameter. Then run the job again.

Source: System Management Facilities (SMF)

..I did not understand what you are saying?

skankatala wrote:Here I am explaining my issue


1. I wrote a cobol program to search a string in particular position.
2. When I try to execute the cobol program using JCL with different input datasets, it is running fine.
3. If input dataset is migrated, the job is running untill the time specified in TIME parameter, and giving S322 abend.
4. If i did not specify any TIME parameter, the job is running for long time and giving S322 at some point.
5. If i specify TIME parameter as 1440, the job is running running and running untill I cancel the job.
6. If i manually recall the dataset while job is in running status, once the recall process is completed before specified time in TIME parameter, job is executing succesfully without any abend.
7. By considering all the above cases, I confirmed that the issue is with Migrated dataset. Please guide me, If I am wrong...

Please help me to resolve this issue....

1. Show us the code please
2. Means nothing except your code runs with that data
3. If the dataset is migrated, it is recalled, as has been pointed out several times, before your program starts, What do you think your program is doing before the dataset is there? Sitting trying to execute an OPEN statement? Try changing the existing DDNAME. The dataset will still come back, then your program wil abend (if coded well) when there is no DD statement for it in the JCL.
4. Probable loop
5. Probable loop, taking even more time because you don't believe your code can be wrong
6. Don't know what you mean by this. The recall is already happening, what are you "manually" doing?
7. By considering all the cases you most likely have a loop in your code

7. By considering all the above cases, I confirmed that the issue is with Migrated dataset. Please guide me, If I am wrong...

Please help me to resolve this issue....