On Dec 19, 2007, at 2:54 PM, Thompson, Steve wrote:
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Ed Gould
Sent: Wednesday, December 19, 2007 1:48 PM
To: [email protected]
Subject: Re: Bad JOB card through NJE
----------SNIP----------------------------
Ok, I know what you are talking about. I have done NJE/RJE with DOS/VS
and above. I have managed to be involved with a similar situation with
JES2 <-> JES3.
The problem here, in my opinion, is that JES2 does not ensure that the
JOB "card" is fully valid. It then sends it to the other JES2 node.
That
node gets it (for some reason minus the ACEE), and then it can't find
the security profile for that JOB. And it can't do it because rather
than coding USER it was coded with USERID. So it is actually being
failed for SYNTAX. But the error message is a security error.
It is my position, that I would like appropriately challenged if one
exists, that JES2 should have "fully" processed the JOB card on the
original system before executing the JES2 command to SEND the JOB. If
the JOB card is syntactically in error, the JOB should be failed on
the
system were submitted as would be the case if that were also the
execution system.
Regards,
Steve Thompson
Steve,
I think I understand your position. Having said that (this goes back
10-15+ years) that there has been an on going issue (not specifically
user= but other items as well) about JES2 and "foreign" job cards,
There was quite a discussion at one GUIDE session about the issue and
(IIRC) everybody agreed to disagree on the problem. I think IBM
(again a long time ago) wavered on the issue some releases it used to
be strict and some releases relaxed the rules I *THINK* somewhere
about 1995 they came up with the current stance. I am pretty sure
(although I could be wrong) they have not really deviated from that
since then. I *THINK* at one time time at (GUIDE?) IBM said it was a
can of worms (I don't remember specifics unfortunately)
I vaguely remember an orange book that talked about some of the
issues. I do not remember the number and I am sure it is out of print
by now but as I recall it did a pretty good job talking about the
issues. I do not specifically recall if a security system was
mentioned in the book (I don't think it was but I don't trust my
dropped bits). I think the orange book did a half way credible
synopsis of the issues. I know I kept the book (at least for a few
years) as every once in while I would come up with a problem and
would refer to it.
IBM got themselves into a bind and couldn't get themselves out of it
so whatever the current rules are, I am not sure you could get anyone
at IBM to either agree to change it or even look at the issue. The
only hint I have (from memory) was the last change to the /*xmit card
was supposed to address most of the issues. If it hasn't perhaps its
time to open a dialog with the JES2 people and get their feedback.
Ed
----------------------------------------------------------------------
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
