Our shop JCL checker (JCLPLUS) flags the open paren of the VOL parm as an error:
Code:
!!!ERROR 8: INVALID KEYWORD PARAMETER: (
And I would tend to agree with that. I would have thought the correst syntax would have been:
Code:
// UNIT=(CART,,DEFER),VOL=(,,,20),
(Note the open paren now comes after the equals sign.)
However, this is how the job is in our prod environment, and it has been running for quite some time this way.
I'm making other changes to the JCL, and I'm considering changing the parm and moving the open parentheses after the equals sign. However, I'm concerned that I may inadvertantly introduce some other sort of error. I'm not real familiar with cartridge tape usage and that sort of thing.
Can anyone tell me if there may be some specific reason WHY it might be coded as it currently is? Also, can someone confirm that my proposed change will not screw anything up; i.e., is
It appears the datsets are simply too large for DASD, so the UNIT overrides were done to write the data to cartridge tape. Also, the primary space on the SORTWKnn cards has a symbolic parm, but the secondary space does not; this appears to be why the SPACE parm was overridden.
And, as you can see, there's that weird (VOL=,,,20), which gets flagged in the JCLPLUS syntax checker, but apparently runs every weekend just fine. Now, the JCL is executed via a job scheduler; maybe it "cleans up" stuff like this? (I think, buyt can't remember now for sure, that I tried to submit the JCL directly in TSO, and that it bombed with a JCL error.
I think in the walkthru I'm going to suggest that we modify the VOL parm, just so oit looks "normal."
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum