I have a batch job that has two steps: the first is a C++ compile and the
second is an ar (archive) BPXBATCH of the object code.
The jobstep for BPXBATCH looks like
//BPXARCH EXEC PGM=BPXBATCH,COND=(4,LT),
// PARM=('SH cd &CSOURCE/Object;',
// ';ar -rvc MyArchive.a #MEMBER#.o')
where #MEMBER# is set to a file name by the submission process. &CSOURCE is
an exported symbol. It all "works perfectly" -- I don't need help
troubleshooting the submission process or symbols or the PARM syntax. That's
not the problem.
I want to know why the job always seems to go to sleep for a minute or two
on that second step. Here's a typical SDSF DA display
JOBNAME StepName ProcStep JobID Owner C Pos DP Real Paging SIO
CPU% ASID ASIDX EXCP-Cnt CPU-Time SR
useridCC *OMVSEX STC04477 userid LO FF 2503 0.00 0.00
0.00 322 0142 891 0.04 DW
useridCC BPXARCH JOB04552 userid A LO FF 530 0.00 0.00
0.00 56 0038 43 0.00 DW
useridCC STEP1 STC04463 userid IN C1 2909 0.00 46.88
0.57 315 013B 59562 5.35
Note how the BPXARCH jobstep has gone into a wait and is swapped out (? Is
that what DP=FF means?). Every time I run the job it sits like this for a
minute or two and then finishes CC=0. Why? How can I make it run more
quickly?
Thanks,
Charles
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
