On 9 February 2012 11:57, Mike Lewis <[email protected]> wrote:
> Early in the life of a STC (earlier, anyway)... the specific START command > text as issued by the operators resides within the CSCB. By the time the > STC's lowly CSECT gains control, the record of the specific START command has > been partially overwritten with other fields. Does anybody know if a record > of the original command resides in memory anywhere? The text isn't provided > with my START CIB. I doubt that it's kept, at least as part of START processing. I believe the CSCB is converted in-situ from the pre execution to the execution version. > I know JES2 has the original command on the spool, and it should therefore be > accessible via SSSO Browse requests. Anybody have any other ideas? This, and the Master Trace that Bill F mentioned, seem like unreliable approaches to me. There are no timing guaranties between START command and your program's execution. SPOOL and trace records of the command may be good for dump-reading forensic activities, but as part of a routine program, I think not. You can probably infer (reverse-engineer, even) an equivalent START command from the JCL constructed for the actual one (in SWA or depending on what you need, just looking at the TIOT and such). What do you need from the command itself that isn't easily available by other means? Tony H. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
