<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic VMS Batch Job in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/vms-batch-job/m-p/3641682#M7977</link>
    <description>I am running Open VMS 7.2-2, TCPWARE 5.4-3 on a two node cluster (ES40's).  The past month I have noticed a batch job which is running but is not getting any cpu time - no error messages - nothing.  It has happened once a week for the past month.  I stop the queue, put the job on hold - let the other jobs run in the queue and then release the job which was not doing anything - it gets processed fine.  While the job is being processed, if I do a show sys the process name is blank and there is still the previous process which I stopped from running.  I can not kill the previous process it claims it is in a suspended state.  The only way I can get rid of it (it really isn't hurting anything to leave it) is to reboot the system.  I have hundreds and hundreds of batch jobs which run through the day fine.  It seems it is this one queue and one job. But, to make it even more strange - the job and queue run fine the majority of the time - just once a week this happens - not at any specific time or with any specific file.   Someone told me I may have a corrupt job controller file which I find hard to believe since it is not happening to all of my jobs or all of my queues.  Has anyone ever seen this - or can give any insight as to what is going on.....??</description>
    <pubDate>Tue, 04 Oct 2005 12:40:28 GMT</pubDate>
    <dc:creator>LM_2</dc:creator>
    <dc:date>2005-10-04T12:40:28Z</dc:date>
    <item>
      <title>VMS Batch Job</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/vms-batch-job/m-p/3641682#M7977</link>
      <description>I am running Open VMS 7.2-2, TCPWARE 5.4-3 on a two node cluster (ES40's).  The past month I have noticed a batch job which is running but is not getting any cpu time - no error messages - nothing.  It has happened once a week for the past month.  I stop the queue, put the job on hold - let the other jobs run in the queue and then release the job which was not doing anything - it gets processed fine.  While the job is being processed, if I do a show sys the process name is blank and there is still the previous process which I stopped from running.  I can not kill the previous process it claims it is in a suspended state.  The only way I can get rid of it (it really isn't hurting anything to leave it) is to reboot the system.  I have hundreds and hundreds of batch jobs which run through the day fine.  It seems it is this one queue and one job. But, to make it even more strange - the job and queue run fine the majority of the time - just once a week this happens - not at any specific time or with any specific file.   Someone told me I may have a corrupt job controller file which I find hard to believe since it is not happening to all of my jobs or all of my queues.  Has anyone ever seen this - or can give any insight as to what is going on.....??</description>
      <pubDate>Tue, 04 Oct 2005 12:40:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/vms-batch-job/m-p/3641682#M7977</guid>
      <dc:creator>LM_2</dc:creator>
      <dc:date>2005-10-04T12:40:28Z</dc:date>
    </item>
    <item>
      <title>Re: VMS Batch Job</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/vms-batch-job/m-p/3641683#M7978</link>
      <description>could you be more precise about the state of your job ? It can be Mutex, RWxxx (Rwast, Rwscs, Rwmpb/Rwmpe,...) . You should instal Amds or Availability Manager (from &lt;A href="http://h71000.www7.hp.com/openvms/system_management.html)" target="_blank"&gt;http://h71000.www7.hp.com/openvms/system_management.html)&lt;/A&gt;    which is often quite helpful.&lt;BR /&gt;&lt;BR /&gt;Could you post the dcl of the job that is a problem ? Which username does it use ? &lt;BR /&gt;&lt;BR /&gt;Are you up to date about your patches for Vms 7.2-2 ?</description>
      <pubDate>Tue, 04 Oct 2005 12:51:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/vms-batch-job/m-p/3641683#M7978</guid>
      <dc:creator>labadie_1</dc:creator>
      <dc:date>2005-10-04T12:51:14Z</dc:date>
    </item>
    <item>
      <title>Re: VMS Batch Job</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/vms-batch-job/m-p/3641684#M7979</link>
      <description>21A0998C BATCH_2008432   LEF      5    12220   0 00:00:01.65      4113   1250  B&lt;BR /&gt;&lt;BR /&gt;LISA_1&amp;gt; show proc/id=21A07AC7 /cont&lt;BR /&gt;%SYSTEM-F-SUSPENDED, process is suspended&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;I will attach the com procedure</description>
      <pubDate>Tue, 04 Oct 2005 13:02:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/vms-batch-job/m-p/3641684#M7979</guid>
      <dc:creator>LM_2</dc:creator>
      <dc:date>2005-10-04T13:02:57Z</dc:date>
    </item>
    <item>
      <title>Re: VMS Batch Job</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/vms-batch-job/m-p/3641685#M7980</link>
      <description>If the process is suspended that is in SUSP state then it was suspended by a SET PROCESS/SUSPEND command or equivilent system service. &lt;BR /&gt;&lt;BR /&gt;Look at &lt;BR /&gt;HELP SET AUDIT/ENABLE&lt;BR /&gt;to see if you can enable auditing for process control system services. If you can in your version of VMS then you will be able to get a record of who suspended the process.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;stopping the queue will suspend the queue.&lt;BR /&gt;&lt;BR /&gt;If the process is not suspended before you stopped the queue then what state was it in?</description>
      <pubDate>Tue, 04 Oct 2005 13:23:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/vms-batch-job/m-p/3641685#M7980</guid>
      <dc:creator>Ian Miller.</dc:creator>
      <dc:date>2005-10-04T13:23:43Z</dc:date>
    </item>
    <item>
      <title>Re: VMS Batch Job</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/vms-batch-job/m-p/3641686#M7981</link>
      <description>Try $ show sys/batch to find the status of the job.&lt;BR /&gt;Show proc says suspended while often it isn't (but is in rwxxx).&lt;BR /&gt;&lt;BR /&gt;Wim</description>
      <pubDate>Tue, 04 Oct 2005 13:34:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/vms-batch-job/m-p/3641686#M7981</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2005-10-04T13:34:14Z</dc:date>
    </item>
    <item>
      <title>Re: VMS Batch Job</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/vms-batch-job/m-p/3641687#M7982</link>
      <description>Or try :&lt;BR /&gt;$ ana/sys&lt;BR /&gt;set proc/Id=xxx&lt;BR /&gt;show proc&lt;BR /&gt;exit&lt;BR /&gt;&lt;BR /&gt;and post the output.&lt;BR /&gt;&lt;BR /&gt;Wim&lt;BR /&gt;</description>
      <pubDate>Tue, 04 Oct 2005 13:38:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/vms-batch-job/m-p/3641687#M7982</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2005-10-04T13:38:12Z</dc:date>
    </item>
    <item>
      <title>Re: VMS Batch Job</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/vms-batch-job/m-p/3641688#M7983</link>
      <description>Process index: 02C7   Name: BATCH_2002318   Extended PID: 21A07AC7&lt;BR /&gt;------------------------------------------------------------------&lt;BR /&gt;Process status:          20044013  RES,DELPEN,PSWAPM,BATCH,PHDRES,ERDACT&lt;BR /&gt;        status2:         00000001  QUANTUM_RESCHED&lt;BR /&gt;&lt;BR /&gt;PCB address              81481E40    JIB address              81791EC0&lt;BR /&gt;PHD address              8B0AA000    Swapfile disk address    00000000&lt;BR /&gt;KTB vector address       8148212C    HWPCB address            8B0AA080&lt;BR /&gt;Callback vector address  00000000    Termination mailbox          0000&lt;BR /&gt;Master internal PID      000F02C7    Subprocess count                0&lt;BR /&gt;Creator extended PID     00000000    Creator internal PID     00000000&lt;BR /&gt;Previous CPU Id          00000001    Current CPU Id           00000001&lt;BR /&gt;Previous ASNSEQ  000000000001E5F1    Previous ASN     00000000000000F2&lt;BR /&gt;Initial process priority        4    Delete pending count            0&lt;BR /&gt;# open files allowed left    1012    Direct I/O count/limit       4094/4096&lt;BR /&gt;UIC                [00001,000126]    Buffered I/O count/limit      511/512&lt;BR /&gt;Abs time of last event   011C0B6D    BUFIO byte count/limit     167760/167952&lt;BR /&gt;ASTs remaining               4094    # of threads                    1&lt;BR /&gt;Swapped copy of LEFC0    00000000    Timer entries allowed left   5000&lt;BR /&gt;Swapped copy of LEFC1    00000000    Active page table count         0&lt;BR /&gt;Global cluster 2 pointer 00000000    Process WS page count        1339</description>
      <pubDate>Tue, 04 Oct 2005 13:41:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/vms-batch-job/m-p/3641688#M7983</guid>
      <dc:creator>LM_2</dc:creator>
      <dc:date>2005-10-04T13:41:14Z</dc:date>
    </item>
    <item>
      <title>Re: VMS Batch Job</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/vms-batch-job/m-p/3641689#M7984</link>
      <description>Also - before I killed the process/queue - it was in the LEF state</description>
      <pubDate>Tue, 04 Oct 2005 13:42:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/vms-batch-job/m-p/3641689#M7984</guid>
      <dc:creator>LM_2</dc:creator>
      <dc:date>2005-10-04T13:42:38Z</dc:date>
    </item>
    <item>
      <title>Re: VMS Batch Job</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/vms-batch-job/m-p/3641690#M7985</link>
      <description>May be the job is submitted with low prio while the others are not.&lt;BR /&gt;&lt;BR /&gt;Do show que/full to find out if something like /prio=1 is present. On a heavy loaded system, it won't get the cpu (in contrast with an HP3000 that gives the cpu to all processes).&lt;BR /&gt;&lt;BR /&gt;Next time the job starts, try set proc/id=xxx/prio=4 (may be several times as it seems to be partly suspended) to get it going.&lt;BR /&gt;&lt;BR /&gt;Wim</description>
      <pubDate>Tue, 04 Oct 2005 13:43:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/vms-batch-job/m-p/3641690#M7985</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2005-10-04T13:43:30Z</dc:date>
    </item>
    <item>
      <title>Re: VMS Batch Job</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/vms-batch-job/m-p/3641691#M7986</link>
      <description>It actually has a priority of 80</description>
      <pubDate>Tue, 04 Oct 2005 13:55:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/vms-batch-job/m-p/3641691#M7986</guid>
      <dc:creator>LM_2</dc:creator>
      <dc:date>2005-10-04T13:55:48Z</dc:date>
    </item>
    <item>
      <title>Re: VMS Batch Job</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/vms-batch-job/m-p/3641692#M7987</link>
      <description>your process has DELPEN, so it is in delete pending.</description>
      <pubDate>Tue, 04 Oct 2005 14:08:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/vms-batch-job/m-p/3641692#M7987</guid>
      <dc:creator>labadie_1</dc:creator>
      <dc:date>2005-10-04T14:08:30Z</dc:date>
    </item>
    <item>
      <title>Re: VMS Batch Job</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/vms-batch-job/m-p/3641693#M7988</link>
      <description>It seems the process is waiting for something. It is waiting to be removed but waiting on the completion of something.&lt;BR /&gt;&lt;BR /&gt;Have to see the dcl (and may be the source code). With anal/sys you may find out what it is waiting for but I'm at home without VMS (and my notes).&lt;BR /&gt;&lt;BR /&gt;Wim</description>
      <pubDate>Tue, 04 Oct 2005 14:12:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/vms-batch-job/m-p/3641693#M7988</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2005-10-04T14:12:10Z</dc:date>
    </item>
    <item>
      <title>Re: VMS Batch Job</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/vms-batch-job/m-p/3641694#M7989</link>
      <description>Labadie,&lt;BR /&gt;&lt;BR /&gt;What about the ERDACT ? &lt;BR /&gt;&lt;BR /&gt;Wim</description>
      <pubDate>Tue, 04 Oct 2005 14:13:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/vms-batch-job/m-p/3641694#M7989</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2005-10-04T14:13:30Z</dc:date>
    </item>
    <item>
      <title>Re: VMS Batch Job</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/vms-batch-job/m-p/3641695#M7990</link>
      <description>the dcl procedure is on my second post as an attachment</description>
      <pubDate>Tue, 04 Oct 2005 14:13:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/vms-batch-job/m-p/3641695#M7990</guid>
      <dc:creator>LM_2</dc:creator>
      <dc:date>2005-10-04T14:13:59Z</dc:date>
    </item>
    <item>
      <title>Re: VMS Batch Job</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/vms-batch-job/m-p/3641696#M7991</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;The process is in ERDACT (executive rundown active). Basically (if I recall correctly) waiting for I/Os to finish (I see 2 DIOs and a couple of BIOs left), and open files to get closed.&lt;BR /&gt;What about a SHOW PROCESS/CHANNEL within SDA.&lt;BR /&gt;&lt;BR /&gt;Kris (aka Qkcl)</description>
      <pubDate>Tue, 04 Oct 2005 15:58:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/vms-batch-job/m-p/3641696#M7991</guid>
      <dc:creator>Kris Clippeleyr</dc:creator>
      <dc:date>2005-10-04T15:58:25Z</dc:date>
    </item>
    <item>
      <title>Re: VMS Batch Job</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/vms-batch-job/m-p/3641697#M7992</link>
      <description>Process active channels&lt;BR /&gt;                            -----------------------&lt;BR /&gt;&lt;BR /&gt;Channel  Window           Status        Device/file accessed&lt;BR /&gt;-------  ------           ------        --------------------&lt;BR /&gt;  0010  00000000                        $1$DKD203:&lt;BR /&gt;  0020  8142C440                        $1$DKC106:[VICTOR.SHARE]EDI_PO_LOAD_FROM&lt;BR /&gt;_EXT.EXE;49&lt;BR /&gt;  0030  811DCF40                        $1$DRA0:[SYSCOMMON.SYSLIB]TPUSHR.EXE;1 (&lt;BR /&gt;section file)&lt;BR /&gt;  0040  811DC9C0                        $1$DRA0:[SYSCOMMON.SYSLIB]DPML$SHR.EXE;1&lt;BR /&gt; (section file)&lt;BR /&gt;  0050  811DAF00                        $1$DRA0:[SYSCOMMON.SYSLIB]CMA$TIS_SHR.EX&lt;BR /&gt;E;1 (section file)&lt;BR /&gt;  0060  811D8B40                        $1$DRA0:[SYSCOMMON.SYSLIB]LIBOTS.EXE;1 (&lt;BR /&gt;section file)&lt;BR /&gt;  0070  811D8800                        $1$DRA0:[SYSCOMMON.SYSLIB]LIBRTL.EXE;1 (&lt;BR /&gt;section file)&lt;BR /&gt;  0080  81249280                        $1$DRA0:[SYSCOMMON.SYSLIB]SQL$INT.EXE;11&lt;BR /&gt; (section file)&lt;BR /&gt;    Press RETURN for more.&lt;BR /&gt;SDA&amp;gt; &lt;BR /&gt;&lt;BR /&gt;Process index: 02C7   Name: BATCH_2002318   Extended PID: 21A07AC7&lt;BR /&gt;------------------------------------------------------------------&lt;BR /&gt;&lt;BR /&gt;Channel  Window           Status        Device/file accessed&lt;BR /&gt;-------  ------           ------        --------------------&lt;BR /&gt;  0090  811DD5C0                        $1$DRA0:[SYSCOMMON.SYSLIB]DECC$SHR.EXE;1&lt;BR /&gt; (section file)&lt;BR /&gt;  00A0  811DA500                        $1$DRA0:[SYSCOMMON.SYSLIB]SORTSHR.EXE;1 &lt;BR /&gt;(section file)&lt;BR /&gt;  00B0  811DA340                        $1$DRA0:[SYSCOMMON.SYSLIB]SMGSHR.EXE;1 (&lt;BR /&gt;section file)&lt;BR /&gt;  00C0  811E6640                        $1$DRA0:[SYSCOMMON.SYSEXE]DCL.EXE;1 (sec&lt;BR /&gt;tion file)&lt;BR /&gt;  00D0  811D5500                        $1$DRA0:[SYSCOMMON.SYSLIB]DCLTABLES.EXE;&lt;BR /&gt;227 (section file)&lt;BR /&gt;  00E0  81754540                        $1$DKD202:[VICDATAEDI.EDI.ARCHIVE.LOG]20&lt;BR /&gt;05100407343803_DNA1W_830_ERL3.LOG;1&lt;BR /&gt;  00F0  8162F7C0                        $1$DKD202:[VICDATAEDI.EDI.COM]EDI_LOAD.C&lt;BR /&gt;OM;34&lt;BR /&gt;  0100  813C2F40                        $1$DRA0:[SYSCOMMON.SYSLIB]RDBSHR.EXE;11 &lt;BR /&gt;(section file)&lt;BR /&gt;  0110  811DAB40                        $1$DRA0:[SYSCOMMON.SYSLIB]LIBOTS2.EXE;1 &lt;BR /&gt;(section file)&lt;BR /&gt;  0120  811DA2C0                        $1$DRA0:[SYSCOMMON.SYSLIB]SCRSHR.EXE;1 (&lt;BR /&gt;section file)&lt;BR /&gt;    Press RETURN for more.&lt;BR /&gt;SDA&amp;gt; &lt;BR /&gt;&lt;BR /&gt;Process index: 02C7   Name: BATCH_2002318   Extended PID: 21A07AC7&lt;BR /&gt;------------------------------------------------------------------&lt;BR /&gt;&lt;BR /&gt;Channel  Window           Status        Device/file accessed&lt;BR /&gt;-------  ------           ------        --------------------&lt;BR /&gt;  0130  811D9FC0                        $1$DRA0:[SYSCOMMON.SYSLIB]LBRSHR.EXE;1 (&lt;BR /&gt;section file)&lt;BR /&gt;  0140  815708C0                        $1$DRA0:[SYSCOMMON.SYSLIB]FORMS$MANAGER.&lt;BR /&gt;EXE;6&lt;BR /&gt;  0150  811D8340                        $1$DRA0:[SYSCOMMON.SYSLIB]EPC$SHR.EXE;1 &lt;BR /&gt;(section file)&lt;BR /&gt;  0160  8150FD00                        $1$DRA0:[SYSCOMMON.SYSLIB]FORMS$CIOSHR.E&lt;BR /&gt;XE;6&lt;BR /&gt;  0170  814F8680                        $1$DRA0:[SYSCOMMON.SYSLIB]FORRTL_D56_TV.&lt;BR /&gt;EXE;1&lt;BR /&gt;  0180  811EB740                        $1$DRA0:[SYSCOMMON.SYSLIB]TIE$SHARE.EXE;&lt;BR /&gt;1 (section file)&lt;BR /&gt;  0190  8149B200                        $1$DRA0:[SYSCOMMON.SYSLIB]LIBRTL_D56_TV.&lt;BR /&gt;EXE;1&lt;BR /&gt;  01A0  811DF8C0                        $1$DRA0:[SYS0.SYSLIB]DEC$FORRTL.EXE;2 (s&lt;BR /&gt;ection file)&lt;BR /&gt;  01B0  811DBFC0                        $1$DRA0:[SYSCOMMON.SYSLIB]EDTSHR.EXE;1 (&lt;BR /&gt;section file)&lt;BR /&gt;  01C0  81042840                        $1$DRA0:[SYS0.SYSLIB]DEC$COBRTL.EXE;2 (s&lt;BR /&gt;ection file)&lt;BR /&gt;  01D0  811DE680                        $1$DRA0:[SYSCOMMON.SYSLIB]DEC$BASRTL.EXE&lt;BR /&gt;;2 (section file)&lt;BR /&gt;  01E0  813BAAC0                        $1$DRA0:[SYSCOMMON.SYSLIB]DBMSHR.EXE;5 (&lt;BR /&gt;section file)&lt;BR /&gt;  01F0  813BAA40                        $1$DRA0:[SYSCOMMON.SYSLIB]DBMPRV.EXE;1 (&lt;BR /&gt;section file)&lt;BR /&gt;    Press RETURN for more.&lt;BR /&gt;SDA&amp;gt; &lt;BR /&gt;&lt;BR /&gt;Process index: 02C7   Name: BATCH_2002318   Extended PID: 21A07AC7&lt;BR /&gt;------------------------------------------------------------------&lt;BR /&gt;&lt;BR /&gt;Channel  Window           Status        Device/file accessed&lt;BR /&gt;-------  ------           ------        --------------------&lt;BR /&gt;  0200  81413440                        $1$DRA0:[SYSCOMMON.SYSLIB]MMPRV.EXE;12 (&lt;BR /&gt;section file)&lt;BR /&gt;  0210  81248F80                        $1$DRA0:[SYSCOMMON.SYSLIB]SQL$SHR.EXE;10&lt;BR /&gt; (section file)&lt;BR /&gt;  0220  811D6B40                        $1$DRA0:[SYSCOMMON.SYSLIB]DTI$SHARE.EXE;&lt;BR /&gt;1 (section file)&lt;BR /&gt;  0230  811DC740                        $1$DRA0:[SYSCOMMON.SYSLIB]NCSSHR.EXE;1 (&lt;BR /&gt;section file)&lt;BR /&gt;  0240  81249A00                        $1$DRA0:[SYSCOMMON.SYSLIB]RDB$SHARE.EXE;&lt;BR /&gt;10 (section file)&lt;BR /&gt;  0250  813C3540                        $1$DRA0:[SYSCOMMON.SYSLIB]RDB$COSIP.EXE;&lt;BR /&gt;11 (section file)&lt;BR /&gt;  0260  811D7D40                        $1$DRA0:[SYSCOMMON.SYSLIB]SECURESHRP.EXE&lt;BR /&gt;;1 (section file)&lt;BR /&gt;  0270  811DA8C0                        $1$DRA0:[SYSCOMMON.SYSLIB]SECURESHR.EXE;&lt;BR /&gt;1 (section file)&lt;BR /&gt;  0280  81249DC0                        $1$DRA0:[SYSCOMMON.SYSLIB]RDMSHR.EXE;12 &lt;BR /&gt;(section file)&lt;BR /&gt;    Press RETURN for more.&lt;BR /&gt;SDA&amp;gt; &lt;BR /&gt;&lt;BR /&gt;Process index: 02C7   Name: BATCH_2002318   Extended PID: 21A07AC7&lt;BR /&gt;------------------------------------------------------------------&lt;BR /&gt;&lt;BR /&gt;Channel  Window           Status        Device/file accessed&lt;BR /&gt;-------  ------           ------        --------------------&lt;BR /&gt;  0290  81360E80                        $1$DRA0:[SYSCOMMON.SYSLIB]RDMSHRP.EXE;12&lt;BR /&gt; (section file)&lt;BR /&gt;  02A0  813A7400                        $1$DRA0:[SYSCOMMON.SYSLIB]RDMPRV.EXE;17 &lt;BR /&gt;(section file)&lt;BR /&gt;  02B0  813BAB40                        $1$DRA0:[SYSCOMMON.SYSMSG]DBMMSG.EXE;4 (&lt;BR /&gt;section file)&lt;BR /&gt;  02C0  813BABC0                        $1$DRA0:[SYSCOMMON.SYSMSG]DBQMSG.EXE;4 (&lt;BR /&gt;section file)&lt;BR /&gt;  02D0  8124A480                        $1$DRA0:[SYSCOMMON.SYSMSG]SQL$MSG.EXE;10&lt;BR /&gt; (section file)&lt;BR /&gt;  02E0  811EAA40                        $1$DRA0:[SYSCOMMON.SYSMSG]SHRIMGMSG.EXE;&lt;BR /&gt;1 (section file)&lt;BR /&gt;  02F0  813BA100                        $1$DRA0:[SYSCOMMON.SYSMSG]RDBMSGS.EXE;11&lt;BR /&gt; (section file)&lt;BR /&gt;  0300  811EAC00                        $1$DRA0:[SYSCOMMON.SYSMSG]TPUMSG.EXE;1 (&lt;BR /&gt;section file)&lt;BR /&gt;  0310  813D3E40                        $1$DRA0:[SYSCOMMON.SYSMSG]COSI$MSG.EXE;1&lt;BR /&gt;1 (section file)&lt;BR /&gt;    Press RETURN for more.&lt;BR /&gt;SDA&amp;gt; &lt;BR /&gt;&lt;BR /&gt;Process index: 02C7   Name: BATCH_2002318   Extended PID: 21A07AC7&lt;BR /&gt;------------------------------------------------------------------&lt;BR /&gt;&lt;BR /&gt;Channel  Window           Status        Device/file accessed&lt;BR /&gt;-------  ------           ------        --------------------&lt;BR /&gt;  0320  811E9C80                        $1$DRA0:[SYSCOMMON.SYSMSG]DECC$MSG.EXE;1&lt;BR /&gt; (section file)&lt;BR /&gt;  0330  8124A0C0                        $1$DRA0:[SYSCOMMON.SYSMSG]SORTMSG.EXE;1 &lt;BR /&gt;(section file)&lt;BR /&gt;  0340  81570740                        $1$DRA0:[SYSCOMMON.SYSMSG]CXXL$MSG_SHR.E&lt;BR /&gt;XE;1&lt;BR /&gt;  0350  814E6D80                        $1$DRA0:[SYSCOMMON.SYSMSG]FORMS$MSGMGRSH&lt;BR /&gt;R.EXE;6&lt;BR /&gt;  0360  813C4D00                        $1$DRA0:[SYSCOMMON.SYSMSG]EPC$MSG.EXE;1 &lt;BR /&gt;(section file)&lt;BR /&gt;  0370  81427600                        $1$DRA0:[SYSCOMMON.SYSMSG]TIE$MESSAGES.E&lt;BR /&gt;XE;1&lt;BR /&gt;  0380  813D3BC0                        $1$DRA0:[SYSCOMMON.SYSMSG]RDMSMSG.EXE;10&lt;BR /&gt; (section file)&lt;BR /&gt;  0390  811DB480                        $1$DRA0:[SYSCOMMON.SYSLIB]TRACE.EXE;1 (s&lt;BR /&gt;ection file)&lt;BR /&gt;  03A0  81706180                        $1$DRA0:[SYSCOMMON.SYSMSG]DBGTBKMSG.EXE;&lt;BR /&gt;1&lt;BR /&gt;  05A0  00000000        Dpnd Busy       $1$DKD202:</description>
      <pubDate>Tue, 04 Oct 2005 16:06:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/vms-batch-job/m-p/3641697#M7992</guid>
      <dc:creator>LM_2</dc:creator>
      <dc:date>2005-10-04T16:06:57Z</dc:date>
    </item>
    <item>
      <title>Re: VMS Batch Job</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/vms-batch-job/m-p/3641698#M7993</link>
      <description>Lisa,&lt;BR /&gt;&lt;BR /&gt;  This case needs to be logged with your local customer support centre.&lt;BR /&gt;&lt;BR /&gt;  Sounds like you're dropping an I/O somewhere. You'll probably need to crash the system and analyze the dump to determine exactly where.&lt;BR /&gt;&lt;BR /&gt;  If it happens again, make sure no one attempts to delete the entry, stop the process or stop the queue. Crash the system and get the dump analyzed.&lt;BR /&gt;&lt;BR /&gt;  Note that OpenVMS engineering won't look at OpenVMS V7.2-2, you'd need to upgrade to V7.3-2 and reproduce the problem there to have it elevated.&lt;BR /&gt;&lt;BR /&gt;  If you don't want to upgrade, make sure you at least have the latest V7.2-2 patches.</description>
      <pubDate>Tue, 04 Oct 2005 19:31:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/vms-batch-job/m-p/3641698#M7993</guid>
      <dc:creator>John Gillings</dc:creator>
      <dc:date>2005-10-04T19:31:49Z</dc:date>
    </item>
    <item>
      <title>Re: VMS Batch Job</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/vms-batch-job/m-p/3641699#M7994</link>
      <description>For the record : ERDACT means Exec mode rundown active.&lt;BR /&gt;&lt;BR /&gt;It seems to be an undocumented process state for sys$getjpi but it is defined in pcbdef.h since at least 6.2 1h3.&lt;BR /&gt;&lt;BR /&gt;Wim</description>
      <pubDate>Wed, 05 Oct 2005 02:07:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/vms-batch-job/m-p/3641699#M7994</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2005-10-05T02:07:00Z</dc:date>
    </item>
    <item>
      <title>Re: VMS Batch Job</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/vms-batch-job/m-p/3641700#M7995</link>
      <description>Lisa,&lt;BR /&gt;&lt;BR /&gt;from your Forum Profile:&lt;BR /&gt;&lt;BR /&gt;&lt;QUOTE&gt;&lt;BR /&gt;I have assigned points to 23 of 45  responses to my questions.&lt;BR /&gt;&lt;/QUOTE&gt;&lt;BR /&gt;&lt;BR /&gt;Maybe you can find some time to do some assigning?&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums1.itrc.hp.com/service/forums/helptips.do?#33" target="_blank"&gt;http://forums1.itrc.hp.com/service/forums/helptips.do?#33&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Mind, I do NOT say you necessarily need to give lots of points. It is fully up to _YOU_ to decide how many. If you consider an answer is not deserving any points, you can also assign 0 ( = zero ) points, and then that answer will no longer be counted as unassigned.&lt;BR /&gt;Consider, that every poster took at least the trouble of posting for you!&lt;BR /&gt;&lt;BR /&gt;To easily find your streams with unassigned points, click your own name somewhere.&lt;BR /&gt;This will bring up your profile.&lt;BR /&gt;Near the bottom of that page, under the caption â  My Question(s)â   you will find â  questions or topics with unassigned points â   Clicking that will give all, and only, your questions that still have unassigned postings.&lt;BR /&gt;&lt;BR /&gt;Thanks on behalf of your Forum colleagues.&lt;BR /&gt;&lt;BR /&gt;PS.  â   nothing personal in this. I try to post it to everyone with this kind of assignment ratio in this forum. If you have received a posting like this before â   please do not take offence â   none is intended!&lt;BR /&gt;&lt;BR /&gt;Proost.&lt;BR /&gt;&lt;BR /&gt;Have one on me.&lt;BR /&gt;&lt;BR /&gt;jpe</description>
      <pubDate>Wed, 05 Oct 2005 04:32:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/vms-batch-job/m-p/3641700#M7995</guid>
      <dc:creator>Jan van den Ende</dc:creator>
      <dc:date>2005-10-05T04:32:13Z</dc:date>
    </item>
    <item>
      <title>Re: VMS Batch Job</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/vms-batch-job/m-p/3641701#M7996</link>
      <description>Lisa&lt;BR /&gt;&lt;BR /&gt;You should first check your patches applied ( $ set term/wid=132 $ prod sh prod/fu $ prod sh hist /fu)&lt;BR /&gt;&lt;BR /&gt;and apply all the latest patches available for Vms 7.2-2 .&lt;BR /&gt;&lt;BR /&gt;Maybe you just lack a few patches and this is not a huge task.&lt;BR /&gt;&lt;BR /&gt;Check at &lt;BR /&gt;&lt;A href="http://www8.itrc.hp.com/service/patch/search.do?BC=patch.breadcrumb.main" target="_blank"&gt;http://www8.itrc.hp.com/service/patch/search.do?BC=patch.breadcrumb.main&lt;/A&gt;|&amp;amp;pageContextName=openvms::&lt;BR /&gt;&lt;BR /&gt;(you will put Alpha and Vms 7.2-2 on the above link)&lt;BR /&gt;&lt;BR /&gt;Only then, if your problem is not solved, you should upgrade to Vms 7.3-2 + all patches.&lt;BR /&gt;&lt;BR /&gt;Good luck</description>
      <pubDate>Wed, 05 Oct 2005 14:27:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/vms-batch-job/m-p/3641701#M7996</guid>
      <dc:creator>labadie_1</dc:creator>
      <dc:date>2005-10-05T14:27:37Z</dc:date>
    </item>
  </channel>
</rss>

