On Wed, 29 Aug 2007 10:49:15 -0500, Paul Gilmartin <[EMAIL PROTECTED]>
wrote:
>On Wed, 29 Aug 2007 15:02:27 +, Ted MacNEIL wrote:
>
>>This has been discussed many times.
>>IBM's design choice is based on a simple premise:
>>When do you convert the system symbols?
>>On the submitting system?
>>
>NJE is NJE. You're thinking of RJE vs RJP.
IIRC, it was called NJP 23 years ago, when I worked in a JES3 shop.
Of course, I only have my memory to go by.
-
Too busy driving to stop for gas!
--
For IBM-MAIN subscribe / signoff /
Ted MacNEIL wrote:
And why does NJE make a difference?
Where do you convert? At the sending or the receiving site?
(NJP is not in my vocabulary).
Network Job Processing (JES3)
NJE is NJE. You're thinking of RJE vs RJP.
--
Edward E Jaffe
Phoenix Software International, Inc
>Rhetorical questions: Why not, then, allow the programmer, through a control
>statement or symbol qualifier, to choose among those three alternatives?
As I already said (and you snipped).
Stop b*tching on IBM-Main and open a requirement with IBM (with a
justification).
-
Too busy driving to s
>And why does NJE make a difference?
Where do you convert? At the sending or the receiving site?
>(NJP is not in my vocabulary).
Network Job Processing (JES3)
-
Too busy driving to stop for gas!
--
For IBM-MAIN subscribe / sign
On Wed, 29 Aug 2007 10:49:15 -0500, Paul Gilmartin <[EMAIL PROTECTED]>
wrote:
>>
>Many programmers feel that even if IBM were to choose one of the
>alternatives above, they would benefit; it would be right for them.
>Those to whom the facility would be no benefit would be not be harmed
>by it if i
On Wed, 29 Aug 2007 15:02:27 +, Ted MacNEIL wrote:
>>(Not that I agree with IBM's design choice here.)
>
>This has been discussed many times.
>IBM's design choice is based on a simple premise:
>When do you convert the system symbols?
>On the submitting system?
>On the converting system?
>On th
On Wed, 29 Aug 2007 15:02:27 +, Ted MacNEIL <[EMAIL PROTECTED]>
wrote:
>>(Not that I agree with IBM's design choice here.)
>
>This has been discussed many times.
>IBM's design choice is based on a simple premise:
>When do you convert the system symbols?
>On the submitting system?
>On the conv
>(Not that I agree with IBM's design choice here.)
This has been discussed many times.
IBM's design choice is based on a simple premise:
When do you convert the system symbols?
On the submitting system?
On the converting system?
On the executing system?
What about NJE/NJP?
Any choice can/will be
On Wed, 29 Aug 2007 07:35:07 -0500, Mark H. Young wrote:
>
>Two different levels of z/OS on each of two LPARs in a MAS. Each image has
>*different* system symbols, like the z/OS level, right? And as part of the DSN
>construct, a variable in the JCL (proc) would translate differently for that
>DS
On Wed, 29 Aug 2007 07:35:07 -0500, Mark H. Young wrote:
>
>Two different levels of z/OS on each of two LPARs in a MAS. Each image has
>*different* system symbols, like the z/OS level, right? And as part of the
DSN
>construct, a variable in the JCL (proc) would translate differently for that
>D
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Mark H. Young
Sent: Wednesday, August 29, 2007 7:35 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: JES2 converter via /*JOBPARM SYSAFF=
But the suggestion to use /*XMIT would work, so that JES2
On Tue, 28 Aug 2007 13:23:43 -0700, Edward Jaffe
<[EMAIL PROTECTED]> wrote:
>Mark H. Young wrote:
>> OK, then how do I submit a batch job on system with z/OS 1.4 and
>> have it execute on system with z/OS 1.7 in that MAS, and have the
>> job resolve the dataset names correctly on the
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Mark H. Young
Sent: Tuesday, August 28, 2007 2:35 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: JES2 converter via /*JOBPARM SYSAFF=
In a JES2 MAS (Multi Access SPOOL) environ with two different
Mark H. Young wrote:
OK, then how do I submit a batch job on system with z/OS 1.4 and have
it execute on system with z/OS 1.7 in that MAS, and have the job
resolve the dataset names correctly on the EXECUTING system?
In JES2, if you code SYSAFF= on the /*JOBPARM statement, convers
On Tue, 28 Aug 2007 20:01:37 +, Ted MacNEIL <[EMAIL PROTECTED]>
wrote:
>>want it to go thru conversion on system (for correct system symbol
resolution), AND for
>execution on system , you would code a:
>/*JOBPARM SYSAFF= correct?
>
>No. Symbol resolution is not supported for bat
>want it to go thru conversion on system (for correct system symbol
>resolution), AND for
execution on system , you would code a:
/*JOBPARM SYSAFF= correct?
No. Symbol resolution is not supported for batch JCL.
This has been discussed many times on the list.
-
Too busy driving to
In a JES2 MAS (Multi Access SPOOL) environ with two different levels of z/OS
running, if you submit a batch job on system , but want it to go thru
conversion on system (for correct system symbol resolution), AND for
execution on system , you would code a: /*JOBPARM SYSAFF=
18 matches
Mail list logo
