RE: V5R3, SBMJOB, and CPD0050

Rob:

I have to amend that. It works fine for some jobs, not others. The job that
fails in this example also fails from the job submitter OR if I submit it
from the command line. But it works if I remove OBJECT as a qualifier for
the program. It's very strange, because jobs on the job submitter with a
qualified program fail the same way whether I submit them from the job
submitter with a 10 or manually do  the SBMJOB from a command line, while
others (which are not in WRKJOBSCDE) are OK if I submit them from a command
line with a qualified program.

Francis Lapeyre
IS Dept. Programmer/Analyst
Stewart Enterprises, Inc.
E-mail: flapeyre@xxxxxxxx 


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Lapeyre, Francis
Sent: Friday, June 9, 2006 8:28 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: V5R3, SBMJOB, and CPD0050

Rob,

Doing a SBMJOB from the command line with a qualified job name works fine. 

Thanks - you may have hit on something. We'll look at the QUSRSYS issue. I'm
copying this message to the operations guy. 

Francis Lapeyre
IS Dept. Programmer/Analyst
Stewart Enterprises, Inc.
E-mail: flapeyre@xxxxxxxx 


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Friday, June 9, 2006 8:09 AM
To: Midrange Systems Technical Discussion
Subject: RE: V5R3, SBMJOB, and CPD0050

Ok, but didn't you say you restored a bunch of stuff from your V5R1 box? 
If you did, and part of what you restored was QUSRSYS, then you need to go 
through the V5R3 upgrade process again.  The concern here is that the 
Object      Type      Library
QDFTJOBSCD  *JOBSCD   QUSRSYS
needs to be converted from a restored V5R1 format to the V5R3 OS that is 
running.

Again, this is one reason that it is STRONGLY suggested that you upgrade a 
box to the current OS before doing this kind of restore to a newer box.

But I seem to remember you also saying that a simple SBMJOB from the 
command line and not the job scheduler is also causing you issues?  Is 
that true?

Rob Berendt