Re: JBA ML - Machine manager & verify allocations -- SYSTEM21

Hi Guys

We are still at good old 3.5.1 but we have had a menu option to run XA705
since we were on 3.4.2. Simply set up a new bespoke task (we have ours in
IN and it uses default LIBL) and have XA705CLP in interactive - voila!

Put it on a menu and you can then authorise a few users to fix their own
problems (has saved me a lot of time over the years!).

Set it up in MM day start with a run time of 12:00:00 and you will get your
noon run.

You WILL get a number of program dumps and fail messages whenever you run
it but it still works.

JBA Studley have made a fix for ICF702 (the actual failing program) which
was supposedly released in a SP late last year. I am still waiting for
their Manchester support to let me know it is now available.

Rgds

Rick Allen
IT Manager
VA EIMCO Australia




Jim_Hawkins@tsss.com@midrange.com on 12/09/2001 00:15:57

Please respond to jbausers-l@midrange.com

Sent by:  jbausers-l-admin@midrange.com  Please respond to
      jbausers-l@midrange.com



To:   jbausers-l@midrange.com
cc:
Subject:  Re: JBA ML - Machine manager & verify allocations



You didn't indicate which version of the system you are at, but.... we have
experienced similar problems a while back.  Tried several things, no luck.
Finally called JBA.   The XA705 cannot be called in any type of batch
situation.  This is supposed to be fixed in a "future" release.  We never
heard any more on this.

In all honesty, I had forgotten about this issue.  We are at V5.2 SP3.  We
have this set up to run in the AS/400 jobscheduler but had the job on hold.
I just tested it and it ran.  So I am guessing it is fixed by SP3.



                    GManoovaloo@ibl.int
                    net.mu                    To:
jbausers-l@midrange.com
                    Sent by:                  cc:
                    jbausers-l-admin@mi       Subject:     JBA ML - Machine
manager & verify allocations
                    drange.com


                    09/11/2001 04:22 AM
                    Please respond to
                    jbausers-l






I have noted an abnormal situation  for quite a time and have not been able
to understand
the cause. I have hesitated to ask for assistance to the group as it might
be something very basic .
However, I do not think I will find the solution all alone . FYI , MMgr was
setup by myself without training/red book- only some help from a JBA
contact  back in 1999. It has worked satisfactorily except for a few
hiccups .
 So here we go :

The following is part of  Day end setup :
============================================================
 MNGADEJOB                 Application Manager                 System:
S44CA805
   Manage Auto Day-End Jobs
   Type options,  press Enter
   1=Select,  2=Override,  3=No override
                       Days        Last
   O   Seqn Job name   SMTWTFS Ovr       Run   Duration  St Description
       0001                   0000000         100901  0:00:45 RS verify
allocations
       0002 IN_TRMSSM    1111111         100901  0:00:02 RS end stk mon
       0003 IN_TRMRM     1111111         100901  0:00:01 RS end reserv. mon
       0004 OE_TRMPM     1111111         100901  0:00:00 RS end price mon.
       0005 OE_TRMIRM    1111111         100901  0:00:00 RS end inv.refr.
mon
       0006 OE_TRMRM     1111111         100901  0:00:00 RS end restrict.
mon
       0007 TS_TRMJOBS 1111111           100901  0:00:01 RS end t/sls
background
       0008                   1111111         100901  0:01:36 RS common
func. day end
       0009                   1111111         100901  0:00:01 RS
application Manager Day
       0010                   1111111         100901  0:00:02 RS clear m/m
log
       0011 TP_TRMMON  1111111  0        081000  0:00:00 RS end
tranp.plan.monitor
                                                          More..
== ===================================================================
Details for Seqn  0001 :

=====================================================================
 Sequence  . . . 0001 Update  Desc verify allocations

 Job name  . . .            Blank for job to be run rather than submitted.




 Request data. . CALL PGM(IPGAMP4/XA705)



 Day mask  . . . 0000000      SMTWTFS Enter 1=Run, 0=No run for each day
 Override  . . .                      1=Force run tonight,  0=Force no run
 Scheduled time  99:99:99 999999 to run at day end
 Schedule group
 Last submitted . 050499 201526   Last job . JOBSCH     QPGMR      419908
 Last run started 100901 220149   Job status . RS Run Successful
 Last run ended . 100901 220234   Duration . .  0:00:45
    Jobs in high intensity are due to run tonight.
    RUNADEJOB has never been executed.
   F3=Exit    F5=Refresh    F8=Add
======================================================================
The above task is in fact  executed every night  despite the day mask .  I
can only suppose that
the system ends up doing what  XA705 is supposed to do as our  application
Manager active/jobq  list
is not growing and we do not have to execute the  Verify Alloc utility ever
day .

A second issue is that we wanted to use OS/400 scheduled job to run  XA705
every day at about noon.
However , the following error occurs :
====================================================================
                                                             System:
S44CA805
 Job . . :   JBAALLOC      User . . :   QSECOFR       Number . . . :
426165
  >> CALL PGM(IPGAMP4/XA705)
     File APG02L01 in library *LIBL not found or inline data file missing.
     Function check. CPF4101 unmonitored by XA705 at statement *N,
instruction
       X'0338'.
     Error message CPF4101 appeared during OPEN (C S D F).

 =================================================================
 Message ID . . . . . . :   CPF4101       Severity . . . . . . . :   40
 Message type . . . . . :   Escape
 Date sent  . . . . . . :   01/09/11      Time sent  . . . . . . :
12:11:01
 Message . . . . :   File APG02L01 in library *LIBL not found or inline
data
   file missing.
 Cause . . . . . :   The file was not opened.  The reason code is 03. The
   reason codes and their meanings are as follows:
     01 - The library does not exist.
     02 - The file does not exist.  The library does exist.
     03 - The file does not exist.  The library specified as *LIBL.
     04 - The file was saved with storage freed.
     07 - An inline data file does not exist.
     08 - A diskette file with SPOOL(*YES) is being opened for a read
operation
   and an inline data file does not exist.
     10 - The file on the remote system does not exist.

More...
 ==================================================================
Please note that a JOBD   containing : Initial library list:
   IPGAMP4
   IPGAMF4
   IPGAMD4
   IPGCFD4
   IPGCFF4
   IPGCFP4
is used to submit this job and  APG02L01 is in fact in  IPGAMF4  .

Sorry for the long post but  I hope that someone can help me with this .
 Thanks beforehand
Gilbert


_______________________________________________
This is the GEAC/JBA System 21 Users (JBAUSERS-L) mailing list
To post a message email: JBAUSERS-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/jbausers-l
or email: JBAUSERS-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/jbausers-l.




_______________________________________________
This is the GEAC/JBA System 21 Users (JBAUSERS-L) mailing list
To post a message email: JBAUSERS-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/jbausers-l
or email: JBAUSERS-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/jbausers-l.