I was more talking about JCL forcing the DD-to-dataset relationships
into one place, which makes them easier to find.
Here's a line I had to mess with last week in a Linux shell script:
$IM_INSTALL_LOCATION/eclipse/IBMIM -input "$SCRIPTHOME/updateSKLM.xml"
While those $ variables are set in that same script, various "if"
statements and other sources make it difficult to figure out what the
end result of the command might be.
On 1/7/2022 1:16 PM, Seymour J Metz wrote:
+There's no forced standard for the choice of ddnames either; you need to know whether
it's INPUT, SYSIN, SYSUT1 or "E. None of the above."
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
________________________________________
From: IBM Mainframe Discussion List [[email protected]] on behalf of Tom
Brennan [[email protected]]
Sent: Friday, January 7, 2022 4:03 PM
To: [email protected]
Subject: Re: ... Re: Top 8 Reasons for using Python instead of REXX for z/OS
Yes, but since there's no forced standard, variables and other methods
mean I might have to look the script or code to figure out what's going
on. Sometimes that can get quite complex with the things people do that
eventually comes up with a filename/path string. JCL makes everything
nice and neat and in one place.
On 1/7/2022 12:01 PM, Seymour J Metz wrote:
Variables and file handles may not be the same as DD names, but they can
serve the same function.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
