Kevin asks:
> We run a program from the Interex CSL called CMONITR to monitor LDEVs and
> abort inactive jobs after a set amount of time.  When we moved from 4.0 to
> 5.5 this program started crashing about every 8-9 days which wreaks havoc
> on some of our nightly batch jobs.  Has anyone else had this problem?

I'm not familiar with CMONITR, but here are some reasons it could be
having problems.

1) The maximum PIN has increased from 1300 (MPE XL 1.1, 2.0) to
   1559 (MPE XL 2.1, 2.2) to 3119 (MPE XL 3.0, 3.1) to
   5460 (MPE/iX 4.0, 4.5) to 8192 (MPE/iX 5.0, 5.5).

2) The maximum LDEV has increased from 999 prior to MPE/iX 4.0
   to 2300 in MPE/iX 4.0 and 4.5, to 4679 in MPE/iX 5.0 and 5.5.

If CMONITR is encounters a PIN or LDEV larger than expected, that
could easily explain the abort.

<plug>

KNOCKOUT, from Lund Performance Solutions, is a supported
product that provides idle job logoff capability.  ... And it
runs on any version of MPE/iX!

See: http://www.lund.com/smngrtbx.htm


Each of the following examples shows a set of KNOCKOUT commands and
briefly discusses their results.

Example #1:

   IDLE JOHN, @.@ = 10
   IDLE @, MGR.SYS = 20  WARN
   IDLE @, @.@ = 99

   Since no SET WARN or SET NOWARN commands were used, and no IDLE
   commands used the NOWARN keyword, all of the sessions will be warned
   before being aborted.

   The session JOHN,MGR.SYS has an idleness limit of 10 (i.e.:  he is
   warned after 10 seconds, then aborted after 10 more), even though the
   jobname, user.account also matches the second IDLE command!

Example #2:

   SET NOWARN
   IDLE JOHN, @.@ = 10
   IDLE @, MGR.SYS = 20
   IDLE @, @.@ = 99

   This works just like the prior example, but users are not warned ...
   instead, they are simply aborted.  When JOHN,MGR.SYS is idle for 10
   seconds...he is aborted.  The SET NOWARN is useful at sites where
   users have learned to respond to the idleness warning by hitting
   return a few times.

Example #3:

   SET NOWARN
   IDLE JOHN, @.@ = 10
   IDLE @, MGR.SYS = 20 WARN
   IDLE MARY, @.S@ = 5
   SET WARN
   SET GLOBAL 34

   When JOHN,MGR.SYS is idle for 10 seconds...he will be aborted without
   warning.  When BEA, MGR.SYS is idle for 20 seconds, she will be
   warned, and then aborted after 20 more idle seconds.
   MARY,MANAGER.SYS will be aborted without warning after 5 seconds.
   What about users who match none of the idle patterns?  They, like
   STEVE.ACCTNG, will be warned after 34 seconds (the GLOBAL value) and
   aborted after 34 more seconds of idleness.

</plug>


--
Stan Sieler                                          [log in to unmask]
                                     http://www.allegro.com/sieler.html