Nice catch! I never considered the effect of PACK. The reason why ISPF allocates and copies to a separate data set is that the JCL on the screen does not necessarily match the current physical content on disk. The JCL may not have been saved yet (or ever), or !aha! it may be PACKed on disk. TSO SUBMIT and apparently the J command read the disk copy directly to the internal reader, so PACKed records are just garbage. I do not PACK my data, so J worked fine for me.
. . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Paul Gilmartin Sent: Thursday, February 15, 2018 3:43 PM To: [email protected] Subject: (External):Re: J line command was: TSO temp dataset On Thu, 15 Feb 2018 16:27:35 -0700, Sri h Kolusu wrote: > >Check if you have PACK ON in your Profile. > >I can replicate your JCL error if the member has PACK ON and I get a >JCL error. > >TYPE PACK OFF while editing the member and save it then try the J >command > PACK is a recurrent source of errors; a manifest misdesign. PACK should be more transparent -- it should be done in the access method, not at any higher stratum, so all utilities could exploit it. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
