On Aug 16, 2011, at 05:44, Steve Comstock wrote: > --------- > > JCL cataloged and in-stream procedures may now > have data set as DD * or DD DATA included > > INCLUDE members may also contain DD * or DD DATA data > Yaaay! It's about time. Can symbol substitution be far behind? (I fear so).
> (the above two points are for JES2 shops only) > Can JES3 be far behind? Well. it caught up with JCL OUTPUT and SDSF. > The JOB statement adds parameter > > JOBRC=MAXRC > JOBRC=LASTRC > JOBRC=(STEP,stepname[.procstepname]) > Is this reported by NOTIFY (Which I haven't used since SDSF became available)? > ISPF / Dialog Manager > > * DSLIST (ISPF 3.4) has new line command: AL - allocate a > file with attributes of filename command is typed over > Yaaay! > The program binder has a new COMPAT value: ZOSV1R13, > which is the first variant of the binder to support > "conditional sequential RLDs" - which I frankly don't > see the need or value of, so maybe somebody can > elighten me on that > I can't even find the doc for that. What is it? > The zOS UNIX obrowse and oedit commands now use the > ISPF browse and edit services (since z/OS 1.11); if > you want to use the previous z/OS UNIX services, set > environment variable BPXWISISP=NO (since z/OS 1.13) > What did they use before? I happen to notice: Usage notes ... 2. obrowse passes the effective UID of its process to the TSO session. If the EUID does not match the EUID of the TSO process, the OBROWSE TSO command will attempt to set the effective UID of the TSO process to that of the shell command prior to loading the file. (no revision bar). It must be in a prior release. It was long desired. Does it restore the prior value on exit? OBROWSE says, "The file name can be absolute or relative." Relative to what? The CWD of the shell, or of the TSO session? > z/OS UNIX has a new command, 'script' that will > capture all commands and responses in a text file > for later processing; looks quite useful > Yaaay! I've previously counseled our Classic-oriented sysprog to log in from a Solaris session and use "script" on Solaris to capture typescripts for problem documentation. A non-POSIX feature for OMVS!? I wonder what sort of Cu$tomer Requirement provoked it? > The z/OS UNIX 'tsocmd' command will propogate file > descriptors 10-99 to the TSO command processor if > you set BPXWRFT=YES > Hmmm. Why not also Rexx "address TSO"? And "10-99" might be frustrating because only 0-9 can readily be used in POSIX shell scripts. -- gil
