home *** CD-ROM | disk | FTP | other *** search
- Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
- Path: sparky!uunet!paladin.american.edu!auvm!UNC.BITNET!UWORKJ
- Message-ID: <IBM-MAIN%92072415095622@RICEVM1.RICE.EDU>
- Newsgroups: bit.listserv.ibm-main
- Date: Fri, 24 Jul 1992 16:06:00 EST
- Sender: IBM Mainframe Discussion list <IBM-MAIN@RICEVM1.BITNET>
- From: 919 Jimmy Workman 962-6501 <UWORKJ@UNC.BITNET>
- Subject: Re: JES2 shutdown problem
- Lines: 21
-
- > We are a new MVS site, and are having problems shutting down JES2. We
- > are following the procedure IBM suggests in the JES2 command reference.
- > We issue a '$p' command, shut down started tasks, and issue a '$p jes2'
- > command. We do not get the '$HASP099 ALL AVAILABLE FUNCTIONS COMPLETE'
- > message when we finish shutting down the started tasks, and get message
- > '$HASP607 JES2 NOT DORMANT - SYSTEM DRAINING' if we try issue the '$p
- > jes2' command at that point. A '$d a,job' commands reports that there
- > are no batch jobs running. A '$d a,stc' reports that 'SYSLOG' and five
- > batch initiators are still running. We can get rid of the batch
- > initiators by issuing '$p i...' commands, but this does not allow the
- > shutdown to complete.
- >
- > Our JES2 is Version 4 Release 2. We have five batch initiators. We have
- > a non-SNA NJE line connected to a VM system by a 3088. We have two SNA
- > RJE lines, which are really connections to JES/328X. We have both
- > LOGON(1) and LOGON(2) definitions, but only the second is actually
- > started. We have no channel-attached unit record equipment.
- >
- > What are we doing wrong?
-
- You will need to drain all lines and the logons.
-