Re: START command when the member is a JOB

2009-08-21 Thread Hunkeler Peter (KIUP 4)
Two thoughts: 

- Have you tried to move the job to the library allocated 
  under //IEFJOBS in the master JCL?
- You might try MGCRE.

-- 
Peter Hunkeler
Credit Suisse

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


Re: START command when the member is a JOB

2009-08-21 Thread Richard Pace
On Thursday 20 August 2009, David Andrews wrote:
 A member in SYS1.PROCLIB is started via operator command.  When I insert
 a JOB statement as the first record, the system executes the member as a
 job (which allows me to use instream data, for example).

 This works well for plain old console START commands, but when I
 internally issue a START command for the same member, and pass a program
 token in the MGCR parameter list, then MVS 1.8 starts the member as a
 plain old started task -- and then jobfails it for the misplaced JOB
 statement.

 I don't see this behavior documented in the JCL reference or the
 Authorized Assembler Services Guide (not saying it isn't there, just
 that I don't see it).  Is this WAD?
I tried what I think you describe on z/OS 1.9.  Seems to work.  Here's what I 
did.  Tell me what's different from your test and I'll try that.  Although, 
it doesn't show here, I tried it with a PTOKEN as well (just changed the 
flag).  That worked also.

*---+1+2+3+4+---
          MODESET KEY=ZERO,MODE=SUP              
          #xdchook ,                             
          SR    R0,R0                            
          MGCR  D_MGCRDATA                       
          MODESET  KEY=NZERO,MODE=PROB           
 * 
 and the parameters:
 
 D_MGCRDATA EQU *                              
          DC    X'80'                          
          DC    AL1(D_MGCRDATA_L1)             
          DC    X''                        
          DC    C'S  X1'                       
 D_MGCRDATA_L1  EQU  *-D_MGCRDATA              
          DC    AL4(0)              Ptoken     
          DC    CL80' security token ' UTOKEN  
 D_MGCRDATA_L2  EQU  *-D_MGCRDATA              
 
 and the proc:
 
 //RGPX1    JOB ,R.G.PACE,NOTIFY=RGP00,MSGCLASS=H    
 //STEP     EXEC PGM=IEFBR14                         
 //SYSIN     DD  *                                   
 JUNK                                                
 JUNK                                                
 //                                           


-- 
Regards,
Richard Pace

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


Re: START command when the member is a JOB

2009-08-21 Thread David Andrews
On Fri, 2009-08-21 at 09:13 -0400, Richard Pace wrote:
 I tried what I think you describe on z/OS 1.9.  Seems to work.

Hrm, maybe it's a 1.8 - 1.9 thing.  I'll have V1.10 in a sandbox in a
couple of weeks, and I can try it there.  In the meantime:

 Tell me what's different from your test and I'll try that.

Our code pretty much matches, unfortunately!

-- 
David Andrews
A. Duda and Sons, Inc.
david.andr...@duda.com

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


Re: START command when the member is a JOB

2009-08-21 Thread Matthew Stitt
Have you set up the IEFJOBS file name in the MSTRJCLxx member?  This allows
you to have job cards, etc for STCs.

On Fri, 21 Aug 2009 11:30:28 -0400, David Andrews d...@lists.duda.com wrote:

On Fri, 2009-08-21 at 09:13 -0400, Richard Pace wrote:
 I tried what I think you describe on z/OS 1.9.  Seems to work.

Hrm, maybe it's a 1.8 - 1.9 thing.  I'll have V1.10 in a sandbox in a
couple of weeks, and I can try it there.  In the meantime:

 Tell me what's different from your test and I'll try that.

Our code pretty much matches, unfortunately!

--
David Andrews
A. Duda and Sons, Inc.
david.andr...@duda.com

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


Re: START command when the member is a JOB

2009-08-21 Thread Richard Pace
On Friday 21 August 2009, David Andrews wrote:
 On Fri, 2009-08-21 at 09:13 -0400, Richard Pace wrote:
  I tried what I think you describe on z/OS 1.9.  Seems to work.

 Hrm, maybe it's a 1.8 - 1.9 thing.  I'll have V1.10 in a sandbox in a

 couple of weeks, and I can try it there.  In the meantime:
  Tell me what's different from your test and I'll try that.

 Our code pretty much matches, unfortunately!
Must be some difference...This works for me on 1.8, 1.9, 1.10, 1.11.


-- 
Regards,
Richard

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


Re: START command when the member is a JOB

2009-08-21 Thread David Andrews
On Fri, 2009-08-21 at 13:44 -0400, Richard Pace wrote:
 Must be some difference...This works for me on 1.8, 1.9, 1.10, 1.11.

The 1.8 system I have at hand is a bit backlevel.  I can try this on my
more up-to-date sandbox, but based on your experience I don't expect any
change.

So... 'tis a puzzlement.  Taking the easy way out, I've removed the
requirement to START this thing as a job.  (Peter and Matthew: I have
not implemented IEFJOBS.  I *can* start jobs, and from SYS1.PROCLIB, but
only from the console, not via internal START with PTOKEN.)

Thanks to all,

-- 
David Andrews
A. Duda and Sons, Inc.
david.andr...@duda.com

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


START command when the member is a JOB

2009-08-20 Thread David Andrews
A member in SYS1.PROCLIB is started via operator command.  When I insert
a JOB statement as the first record, the system executes the member as a
job (which allows me to use instream data, for example).

This works well for plain old console START commands, but when I
internally issue a START command for the same member, and pass a program
token in the MGCR parameter list, then MVS 1.8 starts the member as a
plain old started task -- and then jobfails it for the misplaced JOB
statement.

I don't see this behavior documented in the JCL reference or the
Authorized Assembler Services Guide (not saying it isn't there, just
that I don't see it).  Is this WAD?

-- 
David Andrews
A. Duda and Sons, Inc.
david.andr...@duda.com

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html