Richard Gambrell <[log in to unmask]> replied
 
>Could you let us know more about the nature of the UDC the fails? Just
>what command is being executed? Is it a logon UDC that is failing?
>You might be encountering an error in the execution of a command within
>the UDC which makes it appear to now be "active".
>--
 
The UDC which fails is a logon UDC which just executes a command file.
I know that it is the UDC that fails not the command file as the system
log files tell me that there is no  type 105 record (file close) for the
UDC or even the command file for the particular job/session.
 
The UDC is
LOGON
OPTION NOLIST,LOGON,NOBREAK
XEQ LOGON1.COMMAND.SYSTEM
**************************
 
The command file includes some file equates, setting some JCWs, setting
some system variables and then
IF HP ACCOUNT="SYS" OR HPACCOUNT="SYSTEM" OR HPACCOUNT="OPS" THEN
  SETVAR HPPATH "command.system,opcomm.system,!hpgroup,pub,pub.sys
ELSE
  SETVAR HPPATH "command.system,command,!hpgroup,pub,pub.sys
ENDIF
 
Last night the UDC was bypassed by three jobs on our development 995
each of the jobs logged on at 12:34 AM (together with a host of other jobs)
and on our 918 the UDC was not activated by by 2 jobs and 1 session which
logged on at 23:23 and 23:24. All of these was just after backup in the
startup of our nightly processing run.  So far I have not detected any problems
on our production 995.  I guess during the rest of the day/night the UDC and
Command
file would be stuck in memory because they are or should be accessed by all jobs
and a fair heap of sessions.
 
Many thanks
Bryan O'Halloran