One of the Production job was running for more than 500 minutes and when take a look at the Joblog, it gave the following displays.
03.52.45 JOB20873 IEC502E K 500A,3J0012,SL,PFMEN202,STEP030,PQSS.CLMS.PROF.REPR.G8096V00
03.52.45 JOB20873 IEC501A M 500A,3J0014,SL,COMP,PFMEN202,STEP030.JS010,PQSS.CLMS.PROF.REPR.G8096V00
03.54.52 JOB20873 IEC502E K 500A,3J0014,SL,PFMEN202,STEP030,PQSS.CLMS.PROF.REPR.G8096V00
03.54.52 JOB20873 IEC501A M 500A,3J0016,SL,COMP,PFMEN202,STEP030.JS010,PQSS.CLMS.PROF.REPR.G8096V00
03.56.27 JOB20873 IEC502E K 500A,3J0016,SL,PFMEN202,STEP030,PQSS.CLMS.PROF.REPR.G8096V00
03.56.28 JOB20873 IEC501A M 500A,3J0020,SL,COMP,PFMEN202,STEP030.JS010,PQSS.CLMS.PROF.REPR.G8096V00
03.58.08 JOB20873 IEC502E K 500A,3J0020,SL,PFMEN202,STEP030,PQSS.CLMS.PROF.REPR.G8096V00
03.58.08 JOB20873 IEC501A M 500A,3J0022,SL,COMP,PFMEN202,STEP030.JS010,PQSS.CLMS.PROF.REPR.G8096V00
03.59.26 JOB20873 IEC502E K 500A,3J0022,SL,PFMEN202,STEP030,PQSS.CLMS.PROF.REPR.G8096V00
03.59.26 JOB20873 IEC501A M 500A,282681,SL,COMP,PFMEN202,STEP030.JS010,PQSS.CLMS.PROF.REPR.G8096V00
04.00.59 JOB20873 IEC502E K 500A,282681,SL,PFMEN202,STEP030,PQSS.CLMS.PROF.REPR.G8096V00
04.00.59 JOB20873 IEC501A M 500A,3J0042,SL,COMP,PFMEN202,STEP030.JS010,PQSS.CLMS.PROF.REPR.G8096V00
04.02.47 JOB20873 IEC502E K 500A,3J0042,SL,PFMEN202,STEP030,PQSS.CLMS.PROF.REPR.G8096V00
04.02.47 JOB20873 IEC501A M 500A,283989,SL,COMP,PFMEN202,STEP030.JS010,PQSS.CLMS.PROF.REPR.G8096V00
04.04.54 JOB20873 IEC502E K 500A,283989,SL,PFMEN202,STEP030,PQSS.CLMS.PROF.REPR.G8096V00
04.04.54 JOB20873 IEC501A M 500A,284295,SL,COMP,PFMEN202,STEP030.JS010,PQSS.CLMS.PROF.REPR.G8096V00
04.06.42 JOB20873 IEC502E K 500A,284295,SL,PFMEN202,STEP030,PQSS.CLMS.PROF.REPR.G8096V00
04.06.42 JOB20873 IEC501A M 500A,286181,SL,COMP,PFMEN202,STEP030.JS010,PQSS.CLMS.PROF.REPR.G8096V00
04.08.22 JOB20873 IEC502E K 500A,286181,SL,PFMEN202,STEP030,PQSS.CLMS.PROF.REPR.G8096V00
While Googling, the IEC501A & IEC502E is some thing to do with Tape file. Can you please throw some light on where to start and how to fix this issue?
Joined: 06 Jun 2008 Posts: 8696 Location: Dubuque, Iowa, USA
Quote:
Can you please throw some light on where to start and how to fix this issue?
Your solution is simple -- STOP USING TAPES. These messages indicate the job is M(ounting) various tapes on drive 500A and then unloading the tape with K(eep) specified. If your job cannot be changed to not use tapes, then you cannot do anything about these messages.
Furthermore, it is unlikely that tape mounts were the cause of the long run time -- more likely, the tape mounts are a symptom of a process gone awry. Each tape is mounted for only a minute or two, but if you do enough of them it can add up.
Joined: 23 Nov 2006 Posts: 19244 Location: Inside the Matrix
Hello and welcome to the forum,
Suggest you speak with your storage management people about migrating these datasets to a higher density "tape" - my guess is that these are 3490 (or even 3480) volumes.
I suspect this is "claims history" of some kind and there would be great reluctance to load it all to online dasd and leave it. Depending on how frequently this data is used, it might be copied to dasd and then migrated until the next use. This would prevent the tape mounts, the messages, and would save lots of wall time (depening on now long it takes to recall).
Joined: 09 Mar 2011 Posts: 7309 Location: Inside the Matrix
Definitely talk to storage management. However, describe your problem to them as accurately as you can with all the information you have.
Only if you want to really annoy them, go to them with "suggestions" from the internet up front. They know your site, you know about your program. Only if they don't come up with anything should you, gently, ask about some of the things from here...
