On Fri, 1 Mar 2013 15:59:40 +0930, Anthony Thompson wrote:
>I can only echo Shane's reply. I don't know why you are messing around with
>external utilities when SDSF Rexx provides you with the function you are
>after. Why re-invent the wheel?
> ...
>Of course, non-unique job-names would mean any member would contain the last
>job with that job-name written to the PDS. I'd suggest writing to a
>pre-allocated z/UNIX file (ISFPRTDDNAME) where file-names could be a
>concatenation of job-name and job-number, and use the XFC command instead of
>XDC. See snippet below:
>
I had been unaware of this. Thanks.
>ISFPRTDDNAME = "ANTSDSF"
>
Can I let SVC 99 choose a DDNAME via BPXWDYN( '...rtddn(ISFPRTDDNAME)...')
I assume so.
>ADDRESS TSO "FREE F("ISFPRTDDNAME")"
>
Unnecessary if generated DDN,
> file_name = unix_dir||JNAME.i||"_"||JNUM.i
>
When I "reinvent[ed] the wheel", I chose to put each job step
in a separate directory. Will SDSF respect something such as:
file_name = unix_dir||JNAME.i'/'JNUM.i
> ADDRESS TSO "ALLOC F("ISFPRTDDNAME") PATH('"file_name"') ",
> "PATHDISP(KEEP,KEEP) PATHOPTS(OWRONLY,OCREAT) ",
> "PATHMODE(SIRWXU)"
>
"filedata(BINARY)" is the default. This can be pretty unreadable.
Will SDSF respect a setting of "filedata(TEXT)" instead? (You might
be inclined to say "Of course!", but Binder, for example, overrides
"filedata(TEXT)" to BINARY on SYSLIN. RCF submitted.)
Thanks,
gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
