Two recent examples from my employer's z/OS V2.2 system (sanitized):
//AWKSPLIT EXEC PGM=BPXBATCH,MEMLIMIT=256M
//STDENV DD *
SCRIPT=TSOUSER.TEST.EXEC(AWKSPLIT)
INPUT=TSOUSER.TEST.CSV
//STDPARM DD *
SH echo awk -f "//'$SCRIPT'" "//'$INPUT'"
;
awk -f "//'$SCRIPT'" "//'$INPUT'"
//STDOUT DD SYSOUT=*
//STDERR DD SYSOUT=*
//STDIN DD DUMMY
//
//FLTOFIX EXEC PGM=BPXBATCH,
// PARM='PGM /bin/awk -f //DD:SCRIPT //DD:XTDIN'
//STDOUT DD DISP=(NEW,CATLG,CATLG),
// DSN=TSOUSER.OUTPUT.FILE,
// UNIT=SYSDA,SPACE=(CYL,(5,5),RLSE),
// DSORG=PS,RECFM=VB,LRECL=84,BLKSIZE=0
//STDERR DD SYSOUT=*
//SCRIPT DD *
{ printf "%9s %#015.11f %#015.11f %#015.11f\n", $1, $2, $3, $4 }
//XTDIN DD DISP=SHR,DSN=TSOUSER.INPUT.FILE
//STDIN DD DUMMY
//*
-----Original Message-----
From: IBM Mainframe Discussion List <[email protected]> On Behalf Of
Paul Gilmartin
Sent: Thursday, February 27, 2020 1:11 PM
To: [email protected]
Subject: Re: Rexx parse using period as placeholder
On Thu, 27 Feb 2020 17:31:24 +0000, Farley, Pe
>
>For the record I am personally very comfortable with regexen and use them all
>the time in awk scripts for work (yes, in both z/OS Unix and z/OS JCL) ...
>
???
In which z/OS release did JCL gain support for regexen? I've long wished for
even the most rudimentary string processing in JCL.
--
This message and any attachments are intended only for the use of the addressee
and may contain information that is privileged and confidential. If the reader
of the message is not the intended recipient or an authorized representative of
the intended recipient, you are hereby notified that any dissemination of this
communication is strictly prohibited. If you have received this communication
in error, please notify us immediately by e-mail and delete the message and any
attachments from your system.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
