JES3 is not retarded.
JES3 has this:
//*DATASET parameters.....
//*ENDDATASET
This is what the z/OS MVS JCL REF has for the parameters:
//*DATASET DDNAME=ddname[,parameter]...
The parameters are:
MODE= {E}
{C}
J= {YES}
{NO }
CLASS= {NO }
{MSGCLASS}
{class }
This allows one to put that data in-stream, define what DD will
be using it..... And then the JOB Step that gets it, the data is
encapsulated better than JES2 does it.
So I think this can handle the problem of "IEBUPDTE".
JES3 had lots of interesting features. I noticed MVS getting
those features as we were moving towards SYSPLEX.
Steve Thompson
On 4/14/2024 12:30 PM, Paul Gilmartin wrote:
On Sun, 14 Apr 2024 11:48:02 -0400, Steve Thompson wrote:
In a JES2 environment, DLM= can be up to and including 8
characters (JES3 is limited to 2, not sure of JES3+).
Why is JES3 so retarded? Useful features tend to be added to
JES2 earlier than JES3.
In that case, what odds are there of coming up with a safe string?
Almost certainty for any reasonable file size. The interesting
question then is, "What's the most efficient way to discovedr
a safe string?"
However, IEBUPDTE has no sort of DLM option, so there's
no way to protect data lies beginning with with "./" It's
puzzling that the IEBUPDTE designers never foresaw that
problem. Consider, letting the Devil provide the test case:
/*Rexx
./ADD perverse comment */
say 'Hello, World!'
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
