× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Okay - here it is--

On the new box, the subsystem QBATCHBKUP is active. On the old one (where
everything works), it's inactive.

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 3:16 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: V5R3, SBMJOB, and CPD0050

Peter, I think you've got it!!

                            Display Routing Entries

                                                             System:
STEWART  
 Subsystem description:   QBATCHBKUP     Status:   ACTIVE

 

 Type options, press Enter.

   5=Display details

 

 
Start 
 Opt    Seq Nbr    Program       Library       Compare Value
Pos  
           10      QCL           QSYS          'QCMDB'
1   
          500      *RTGDTA                     'PGMEVOKE'
29   
         9999      QCL           QSYS          *ANY

 

                                                                         


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: Friday, June 9, 2006 2:53 PM
To: Midrange Systems Technical Discussion
Subject: Re: V5R3, SBMJOB, and CPD0050

Hi Francis,

The joblog you posted shows the routing data:

002759/EMERGENCY/QPADEV0004. Job 002799/EMERGENCY/TEST99 was started using
the Submit Job
(SBMJOB) command with the following job attributes: JOBPTY(5) OUTPTY(5)
PRTTXT() *RTGDTA(QCMDB)* SYSLIBL(QSYS      QSYS2      QHLPSYS    QUSRSYS)
CURLIB(*CRTDFT) INLLIBL(QTEMP      QGPL    ARDTACM    ARDTASC    OBJECT
SOURCE     GLHDSDATA  HDSMODPGM  HDSSTDPGM SHROBJECT  WM400) LOG(4 00
*SECLVL)

and your routing entries for QBATCH should end up using sequence 9999, 
or QSYS/QCMD, which is what you'd like:

QBATCH routing data looks the same as yours:
Start 
 Opt    Seq Nbr    Program       Library       Compare Value Pos  
          15      QCMD          QSYS          'QIGC'          1   
         300      QCMD          QSYS          'QS36EVOKE'     1   
         700      QCL           QSYS          'QCMD38'        1   
        9999      QCMD          QSYS          *ANY

I don't know if this is odd or not, but the joblog also says:

Message . . . . :   Job 002799/EMERGENCY/TEST99 started on 06/09/06 at
08:34:14 in subsystem QBATCHBKUP.

Notice that it started in subsystem QBATCHBKUP.  You said "QBATCH routing
data".  Is that routing data from the QBATCHBKUP subsystem?

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

/

Lapeyre, Francis wrote:
I can compile just fine. The problem is I think, one of our JOBDs points
to
a routing entry that does a SBMJOB in S/38 mode.

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


  


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.