In a recent note, john gilmore said:
Date: Fri, 27 May 2005 22:35:28 +
The JCL manual snippet quoted by Paul Gilmartin,
The system ignores all parameters other than DUMMY or
DSNAME=NULLFILE and DCB. The DCB parameter must be coded if you
would code it for normal I/O
It depends on how backleveled your customers are (might be), and
how will your products react to an 0C1?
PLO is now older than dirt. Your customer would have to be on an
ECL machine, or a 1st generation CMOS. PLO came in with G2 CMOS.
I seriously doubt there are ANY production systems in use
In a recent note, Charles Mills said:
Date: Fri, 27 May 2005 16:16:26 -0700
I don't consider the problem interesting enough to try the experiment,
but I think you are mistaken. I am relatively certain that
I would not so impugn either John G's veracity or his observational
acuity
Craddock, Chris wrote:
... PLO came in with G2 CMOS.
No. PLO was introduced with G3 CMOS. (I can still remember being jealous
that our little P/390 running VM and VSE had PLO while our big
two-way 9672-R22 running MVS didn't.) PLO was later retrofitted to G2
along with several other
In a message dated 5/28/2005 12:36:28 P.M. Central Standard Time,
[EMAIL PROTECTED] writes:
hardware and software... they aren't spending any money! Why would
anyone go to that amount of trouble when there's no revenue in it
anyway? Charity?
Politics, delivery schedules, security.
So, the JCL C/I is not behaving as specified. Does anyone want to raise
a PMR?
The JCL is behaving exactly as the manual indicates it would. There can
certainly be no account in the JCL manual for utilities or programs that do
additional validation (such as IEBGENER).
The JCL is certainly
You are missing the JOB card continuation.
Please note that the JOB card continuation MUST have // in columns 1-3
and the first non-blank character of the JOB card continuation MUST occur no
later than column 16.
John P Baker
Software Engineer
-Original Message-
From: IBM Mainframe
Would love to see the entire JOB Card. The illegal job card statement maybe
due to a parm later in the statement. What you have supplied shows a
continuation comma but do not see any additional cards. Plus I am not seeing
any message id for the message. Do you have a jobcard exit that might be
You have two approaches; which one I'd recommend is based upon how you want
to determine whether the A/S should intercept or not.
If your situation allows a module of yours to get control once you
determine if you want to intercept for the A/S, then SVC screening might be
practical. Do you
9 matches
Mail list logo
