RE: V5R3, SBMJOB, and CPD0050

["Lapeyre, Francis" <FLAPEYRE@xxxxxxxx>]

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 


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jerry Adams
Sent: Thursday, June 8, 2006 2:16 PM
To: Midrange Systems Technical Discussion
Subject: Re: V5R3, SBMJOB, and CPD0050

Francis,


There's got to be more to this.  I just ran a command like SBMJOB and a 
WRKJOBSCDE entry with the library name as a qualifier:


SBMJOB CMD(CALL PGM(MYLIB/ARL002C))


Both ran fine.


Did you use the same program and library for the SBMJOB test that you 
reported with the WRKJOBSCDE problem?  If so, might the problem be with 
the called program? 


        * Jerry C. Adams
*IBM System i Programmer/Analyst
B&W Wholesale Distributors, Inc.* *
voice
        615.995.7024
fax
        615.995.1201
email
        jerry@xxxxxxxxxxxxxxx <mailto:jerry@xxxxxxxxxxxxxxx>



Lapeyre, Francis wrote:

> Also, this happens with any ordinary SBMJOB from the command line.
>
> Francis Lapeyre
> IS Dept. Programmer/Analyst
> Stewart Enterprises, Inc.
> E-mail: flapeyre@xxxxxxxx 
>
>