Re: [SYS21] Machine Manager problem -- SYSTEM21

We had what sounds like the same problem and traced it back to some bogus
records we found in 3 files...
The cause of the bogus records being created escapes me now but I do believe it
was introduced in a System Manager PTF...
Someone else might remember or perhaps it could be found in an archive
somewhere...

Run a qyery over these files and see if you have any "AC" records in them...
And as always be sure to back up the files before you delete anything...

We now run this program (see below) every night just before we run Machine
Manager...
This will clear out the bogus records...

Please note that we do not have "AC" (Advanced Customer Scheduling) installed on
our box...
If you are using "AC" then this may not be a valid solution for you...

Let me know if this solves your problem...
Good luck...

Columns . . . : 1 100 Browse
SYSUT/ALLSRC
SEU==>
ACCLEANUP
FMT ** ...+... 1 ...+... 2 ...+... 3 ...+... 4 ...+... 5 ...+... 6 ...+... 7
...+... 8 ...+... 9 ...+... 0
*************** Beginning of data
***************************************************************************************

0001.00 PGM
951110
0001.01 MONMSG MSGID(CPF0000)
001228
0001.02
000419
0001.03 RUNSQL REQUEST('delete from apg01phy where -
000419
0001.04 appl01 = ''AC''')
001031
0001.05
000419
0001.06 RUNSQL REQUEST('delete from apg02phy where -
000419
0001.07 appl02 = ''AC''')
001031
0001.08
000419
0001.09 RUNSQL REQUEST('delete from apg99phy where -
000419
0001.10 l#appn = ''AC''')
001031
0001.11
000419
0310.00 ENDPGM
890808
****************** End of data
******************************************************************************************

Stuart Sandler <SSandler@KREBS.COM> on 01/28/2003 11:55:48 AM

Please respond to "GEAC/JBA System 21 Users" <jbausers-l@midrange.com>

To: "'JBAUSERS-L@midrange.com'"
<JBAUSERS-L@midrange.com>

cc: (bcc: Jeff Klipa/Harvard)

Subject [SYS21] Machine Manager problem
:

I was wondering if anyone had any suggestions to help me with a MM problem.

We recently upgraded our hardware and OS and all seems to be working fine.
However, my Machine Manager seems to loop at the end of the Day End process.
By looping, I mean generating a 1000 page job log every few minutes.

The majority of the messages are along the lines of the following:

DATE TIME FROM PGM LIBRARY INST TO PGM
LIBR
opened with the SEQONLY(*YES) parameter specified in the program or on the

Override Database File (OVRDBF) command. However, the parameter has been

changed to SEQONLY(*NO) because of condition 1 shown below: 1 - The program

opened member AMM95PHY for output operations only and SEQONLY(*YES) was

specified with the default number of records. SEQONLY(*YES) was changed to

SEQONLY(*NO) to allow the program to handle duplicate key, conversion

mapping, key mapping, and select or omit errors, or both select and omit

errors at the time of the output operation. 2 - The program opened the

member for other than input or output operations only. 3 - The program

opened a logical file member for output operations only and that member is

based on more than one physical file member. 4 - The record length plus the

feedback information for the member is greater than 32,767 bytes. 5 - The

commitment control level of *ALL is active and the member was opened for

input operations only, or the commitment control levels of either *ALL, *CS,

or *CHG were specified for a distributed file that was opened for input

Does anyone have any suggestions?

Thanks,

Stuart Sandler
Director of Information Systems
Krebs Engineers
(520) 744 - 5601
ssandler@krebs.com

_______________________________________________
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/mailman/listinfo.cgi/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.