|
No, it's straight CL - no QCAEXC. This happens from the job scheduler or when I do a SBMJOB from a command line and qualify the library of the program. If you either leave out the library, or call it without the SBMJOB (but with a library in the PGM parameter), it's fine. 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 Peter Dow (ML) Sent: Thursday, June 8, 2006 3:31 PM To: Midrange Systems Technical Discussion 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
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.