Currently, "2" will be treated the same as "0" or " " (blank). There is no reason why you should have specified "2", and a good reason not to - there is a possibility that in some future release, we might assign some meaning to "2".
Standalone dump treats this character as a hexadecimal digit representing four option bits. The first bit is an undocumented option intended to be used only under my direction. The second bit is what is documented for "4". The third (corresponding to "2") and fourth bits are currently unused. Jim Mulder z/OS Diagnosis, Design, Development, Test IBM Corp. Poughkeepsie NY > Back in 2010 I had a system coded with SADUMP(xxxx,SNSYSC2) and MVS(LAST). > > When a > > V, XCF,sysn,OFFLINE,SADUMP,REIPL > > command was issued, the system did take a Stand Alone Dump, and did IPL. > > That is my recollection. > > Today I have no idea why I coded the "2" in the "SSNSYSC2" > loadparm, and was hoping someone could explain why it worked. > > The SADUMP manual says that only "0", "4" and " " (blank) are valid values. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
