In a recent note, Ted MacNEIL said:
> Date: Thu, 29 Dec 2005 12:12:42 -0500
>
Hmmm. I notice your timestamp is no longer flashing midnight
like a lobotomized VCR. Hasn't been since Nov. 10.
> >//STEP1 EXEC
> PGM=IEFBR14
> >//TEST DD DSN='BAB.TEST.TEST
> (0)',UNIT=SYSALLDA,
> >// SPACE=(TRK,1),DISP=
> (,CATLG),VOL=SER=SH20C0
>
... but your lines are still wrapped ala Blackberry. Did RIM
fix the broken timestamp syntax, did LISTSERV accommodate the
breakage, or are you posting from Blackberry via the WWW interface?
> NAMED IN QUOTES, IS NOT ELIGIBLE TO BE SMS-
> MANAGED
>
Now this is interesting. I had to try it myself. More completely:
10.39.42 JOB08819 IEF452I SMSNAME - JOB NOT RUN - JCL ERROR
[ ... ]
4 IEF648I INVALID DISP FIELD- KEEP SUBSTITUTED
4 IGD316I DATA SET ALLOCATION REQUEST FAILED -
DATA SET - ' A...(0) '
NAMED IN QUOTES, IS NOT ELIGIBLE TO BE SMS-MANAGED
It's an IGD* message, not an IEF* message. SMS is doing it, not
JCL Converter. But JCL must communicate closely with SMS to do
this -- the sort of design I advocated in a prior post.
But how does SMS know the JCL text contained quotes? Doesn't
the JCL converter strip them off and use only the interior content
as the data set name? And why should SMS care how the name was
represented in JCL, as long as it's valid after lexical processing?
-- gil
--
StorageTek
INFORMATION made POWERFUL
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
