RE: V5R3, SBMJOB, and CPD0050

Jim. Thanks. No, this is V5R3M0, as far as I know.

I'll pass that along to Operations.

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 Jim Franz
Sent: Friday, June 9, 2006 10:45 AM
To: MIDRANGE-L@xxxxxxxxxxxx
Subject: Re: V5R3, SBMJOB, and CPD0050

I would suggest (as you said) this is very strange.
Something is not right about how this box is setup.
2 suggestions to check :
a. If the security audit log is turned on, review any entries around these 
errors. The error msg does not indicate security, but error msg may not be 
the real problem.

b. Compare the following with a working v5r3 system
    Job descriptions involved (all parms)
    subsystem descriptions, especially routing data
    class descriptions

Also - are you at V5R3 or V5R3M5 ?

I have had new i5 server, pre-loaded, coming with strange stuff IBM left on 
machine from their tests.
Ruling out everything - this is not loaded with V5R3 pre-release cd's?

and call IBM Support if available.

Jim Franz


----- Original Message ----- 
From: "Lapeyre, Francis" <FLAPEYRE@xxxxxxxx>
To: "'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
Sent: Friday, June 09, 2006 10:47 AM
Subject: RE: V5R3, SBMJOB, and CPD0050

From DSPJOBLOG on the session I did the submit from:

3 > SBMJOB CMD(CALL PGM(OBJECT/ARR745JQ)) JOB(TEST99) JOBD(ARDTASC/ARJOBD)
JOBQ(QBATCH)

   Job 002799/EMERGENCY/TEST99 submitted to job queue QBATCH in library
QGPL.

Looks OK from the display session, but the submitted job blows up.

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 9:15 AM
To: Midrange Systems Technical Discussion
Subject: RE: V5R3, SBMJOB, and CPD0050

Try submitting it from the command line, and posting the part of the job
log where the submit was done.  You may have to do a DSPJOBLOG to find it.

Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





"Lapeyre, Francis" <FLAPEYRE@xxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
06/09/2006 09:45 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
"'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
cc

Subject
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
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





"Lapeyre, Francis" <FLAPEYRE@xxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
06/09/2006 08:39 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
"'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
cc

Subject
RE: V5R3, SBMJOB, and CPD0050






It's a completely new box which came with V5R3 already there.

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 kirkg@xxxxxxxxxxxxx
Sent: Thursday, June 8, 2006 4:03 PM
To: Midrange Systems Technical Discussion
Subject: Re: V5R3, SBMJOB, and CPD0050

OK I bet you blew up QUSRSYS... You did re-install/upgrade QUSRSYS after
the upgrade? and you have IPL'd since that restore?

Do a GO LICPGM and then #10 is QUSRSYS and/or QGPL down level?


Kirk Goins CCNA
Systems Engineer, Manage Inc.
IBM Certified i5 Solution Sales
IBM Certified iSeries Solutions Expert
IBM Certified Designing IBM e-business Solutions
Office 503-353-1721 x106 Cell 503-577-9519
kirkg@xxxxxxxxxxxxx      www.manageinc.com

There are 10 types of people in the world:
Those that understand binary, and those that don't.



"Peter Dow (ML)" <maillist@xxxxxxxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
06/08/2006 01:30 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
cc

Subject
Re: V5R3, SBMJOB, and CPD0050







Hi Francis,

Sounds like it's using System/38 naming conventions.  Did you at some
point call QCAEXEC instead of QCMD?

*Peter Dow* /
Dow Software Services, Inc.
909 793-9050
pdow@xxxxxxxxxxxxxxx <mailto:pdow@xxxxxxxxxxxxxxx> /

Lapeyre, Francis wrote:

No - the thing is that we restored this machine from our current

production

machine (at V5R1) for testing. The program exists in OBJECT in both

places.

It's the same program; hasn't been changed since 2001. And this showed

up

with another job schedule entry - so I did a SBMJOB from the command

line,

qualifying the library, and it fails on V5R3, but works on V5R1.

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

-- 
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


-- 
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
-- 
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


-- 
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
-- 
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
-- 
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


-- 
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
-- 
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.