Re: JES2 shutdown failure - OMVS will not shut down

2019-05-15 Thread Brian Westerman 
At the point in time where I shut down ZFS, I want it to interfere, that's the 
whole point.

Brian

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: JES2 shutdown failure - OMVS will not shut down

2019-05-15 Thread Steve Horein 
IBM indicates ZFS is handled with ending OMVS:

"In general, do not stop zFS. Stopping zFS is disruptive to applications
that are using zFS file systems. zFS stops automatically when you shut down
z/OS® UNIX. To shut down an LPAR or to re-IPL an LPAR, use the MODIFY
OMVS,SHUTDOWN operator command to shut down z/OS UNIX. This action
synchronizes data to the file systems and unmounts or moves ownership in a
shared file system environment. A planned system shutdown must include the
unmount or move of all owned file systems and the shut down of zFS. The
MODIFY OMVS,SHUTDOWN command unmounts and moves the owned file systems and
shuts down zFS. For shutdown procedures using F OMVS,SHUTDOWN, see Planned
shutdowns using F OMVS,SHUTDOWN

 in z/OS UNIX System Services Planning

."

https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.3.0/com.ibm.zos.v2r3.ioea700/stopzfs.htm



On Wed, May 15, 2019 at 12:47 AM Brian Westerman <
brian_wester...@syzygyinc.com> wrote:

> you left ZFS running.  It should come down before you issue the commands
> you listed.  As in:
>
> F OMVS,STOPPFS=ZFS
> F BPXOINIT,SHUTDOWN=FORKINIT
> SETRRS SHUTDOWN
> F OMVS,SHUTDOWN
> /DU,STA
> /PJES2
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: JES2 shutdown failure - OMVS will not shut down

2019-05-14 Thread Brian Westerman 
you left ZFS running.  It should come down before you issue the commands you 
listed.  As in:

F OMVS,STOPPFS=ZFS
F BPXOINIT,SHUTDOWN=FORKINIT
SETRRS SHUTDOWN
F OMVS,SHUTDOWN
/DU,STA
/PJES2

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: JES2 shutdown failure - OMVS will not shut down

2019-05-14 Thread Mike Schwab 
Any system tasks using an OMVS file?

On Tue, May 14, 2019 at 10:07 PM Tony Thigpen  wrote:
>
> As everything indicates that OMVS was the problem, I brought the machine
> back up and try shutting down OMVS outside of my system shutdown. This
> is the results:
>
> 22.02.52 HUP1   F BPXOINIT,SHUTDOWN=FORKINIT
> 22.02.52 HUP1   BPXM037I BPXAS INITIATOR SHUTDOWN DELAYED.
> 22.02.52 HUP1 STC03368  IEF404I BPXAS - ENDED - TIME=22.02.52
> 22.02.52 HUP1 STC03334  IEF404I BPXAS - ENDED - TIME=22.02.52
> 22.02.52 HUP1 STC03368  $HASP395 BPXASENDED
> 22.02.52 HUP1 STC03369  IEF404I BPXAS - ENDED - TIME=22.02.52
> 22.02.52 HUP1 STC03334  $HASP395 BPXASENDED
> 22.02.52 HUP1 STC03370  IEF404I BPXAS - ENDED - TIME=22.02.52
> 22.02.52 HUP1 STC03369  $HASP395 BPXASENDED
> 22.02.52 HUP1 STC03370  $HASP395 BPXASENDED
> 22.03.16 HUP1   F OMVS,SHUTDOWN
> 22.03.16 HUP1   IEE342I MODIFY   REJECTED-TASK BUSY
>
> Thoughts?
>
> Tony Thigpen
>
> Tony Thigpen wrote on 5/14/19 5:55 PM:
> > F BPXOINIT,SHUTDOWN=FORKINIT
> > BPXM036I BPXAS INITIATORS SHUTDOWN.
> > F OMVS,SHUTDOWN
> > IEE342I MODIFY   REJECTED-TASK BUSY
> >
> > Tony Thigpen
> >
> > Cieri, Anthony wrote on 5/14/19 5:50 PM:
> >> Under the OAS column of your D A,L display there is still one task.
> >>
> >> Was a $P JES2 command ever issued. Usually, when we are at this
> >> point in a DR environment and the $P JES2 command is issued, JES2 may
> >> tell you what is still active if the stop command fails.
> >>
> >> Here are some other possibly useful commands:
> >>
> >> F BPXOINIT,SHUTDOEN=FORKINIT
> >> F OMVS,SHUTDOWN
> >>
> >> Hth
> >> Tony
> >>
> >> -Original Message-
> >> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> >> On Behalf Of Jerry Whitteridge
> >> Sent: Tuesday, May 14, 2019 5:40 PM
> >> To: IBM-MAIN@LISTSERV.UA.EDU
> >> Subject: Re: JES2 shutdown failure
> >>
> >> [[ SEI WARNING *** This email was sent from an external source. Do not
> >> open attachments or click on links from unknown or suspicious senders.
> >> *** ]]
> >>
> >>
> >> I'd be suspicious of your OMVS environment at this point. Try using a
> >> D A,A
> >> to see more tasks active.
> >>
> >> Jerry Whitteridge
> >> Delivery Manager / Mainframe Architect
> >> GTS - Safeway Account
> >> 602 527 4871 Mobile
> >> jerry.whitteri...@ibm.com
> >>
> >> IBM Services
> >>
> >> IBM Mainframe Discussion List  wrote on
> >> 05/14/2019 02:35:25 PM:
> >>
> >>> From: Brian France 
> >>> To: IBM-MAIN@LISTSERV.UA.EDU
> >>> Date: 05/14/2019 02:35 PM
> >>> Subject: [EXTERNAL] Re: JES2 shutdown failure
> >>> Sent by: IBM Mainframe Discussion List 
> >>>
> >>> init's drained?   lines drained? omvs shutdown?
> >>>
> >>> On 5/14/19 5:32 PM, Tony Thigpen wrote:
>  I am testing on a DR box, and I am seeing a shutdown problem with JES2.
> 
>  Here is the console log:
>  $da
>  $HASP612 NO ACTIVE JOBS
>  $P JES2
>  IEA964I HARDCOPY SUSPENDED, REASON=HCSW
>  $da
>  IEE707I $DA  NOT EXECUTED
>  D A,L
>   JOBS M/STS USERSSYSASINITS   ACTIVE/MAX VTAM
> >> OAS
>  020  0002500/0
> >> 1
>   JES2 JES2 IEFPROC  NSW  S  SHUTHUP1 SHUTHUP1 COMAND00 OWT
> >> S
> 
>  At this point, JES2 never seems to shut down. (The only job running is
>  SHUTHUP1 which is the automated shutdown procedure that runs outside
>  of JES2.)
> 
>  Thoughts?
> 
> >>> --
> >>> Brian W. France
> >>> Systems Administrator (Mainframe)
> >>> Pennsylvania State University
> >>> Administrative Information Services - Infrastructure/SYSARC
> >>> Rm 25 Shields Bldg., University Park, Pa. 16802
> >>> 814-863-4739
> >>> b...@psu.edu
> >>>
> >>> "To make an apple pie from scratch, you must first invent the universe."
> >>>
> >>> --
> >>> For IBM-MAIN subscribe / signoff / archive access instructions,
> >>> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
> >>>
> >>
> >> --
> >> For IBM-MAIN subscribe / signoff / archive access instructions,
> >> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
> >>
> >> --
> >> For IBM-MAIN subscribe / signoff / archive access instructions,
> >> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
> >>
> >>
> >
> > --
> > For IBM-MAIN subscribe / signoff / archive access instructions,
> > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
> >
> >
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu

Re: JES2 shutdown failure - OMVS will not shut down

2019-05-14 Thread Tony Thigpen 
As everything indicates that OMVS was the problem, I brought the machine 
back up and try shutting down OMVS outside of my system shutdown. This 
is the results:


22.02.52 HUP1   F BPXOINIT,SHUTDOWN=FORKINIT
22.02.52 HUP1   BPXM037I BPXAS INITIATOR SHUTDOWN DELAYED.
22.02.52 HUP1 STC03368  IEF404I BPXAS - ENDED - TIME=22.02.52
22.02.52 HUP1 STC03334  IEF404I BPXAS - ENDED - TIME=22.02.52
22.02.52 HUP1 STC03368  $HASP395 BPXASENDED
22.02.52 HUP1 STC03369  IEF404I BPXAS - ENDED - TIME=22.02.52
22.02.52 HUP1 STC03334  $HASP395 BPXASENDED
22.02.52 HUP1 STC03370  IEF404I BPXAS - ENDED - TIME=22.02.52
22.02.52 HUP1 STC03369  $HASP395 BPXASENDED
22.02.52 HUP1 STC03370  $HASP395 BPXASENDED
22.03.16 HUP1   F OMVS,SHUTDOWN
22.03.16 HUP1   IEE342I MODIFY   REJECTED-TASK BUSY

Thoughts?

Tony Thigpen

Tony Thigpen wrote on 5/14/19 5:55 PM:

F BPXOINIT,SHUTDOWN=FORKINIT
BPXM036I BPXAS INITIATORS SHUTDOWN.
F OMVS,SHUTDOWN
IEE342I MODIFY   REJECTED-TASK BUSY

Tony Thigpen

Cieri, Anthony wrote on 5/14/19 5:50 PM:

Under the OAS column of your D A,L display there is still one task.

Was a $P JES2 command ever issued. Usually, when we are at this 
point in a DR environment and the $P JES2 command is issued, JES2 may 
tell you what is still active if the stop command fails.


Here are some other possibly useful commands:

F BPXOINIT,SHUTDOEN=FORKINIT
F OMVS,SHUTDOWN

Hth
Tony

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
On Behalf Of Jerry Whitteridge

Sent: Tuesday, May 14, 2019 5:40 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: JES2 shutdown failure

[[ SEI WARNING *** This email was sent from an external source. Do not 
open attachments or click on links from unknown or suspicious senders. 
*** ]]



I'd be suspicious of your OMVS environment at this point. Try using a 
D A,A

to see more tasks active.

Jerry Whitteridge
Delivery Manager / Mainframe Architect
GTS - Safeway Account
602 527 4871 Mobile
jerry.whitteri...@ibm.com

IBM Services

IBM Mainframe Discussion List  wrote on
05/14/2019 02:35:25 PM:


From: Brian France 
To: IBM-MAIN@LISTSERV.UA.EDU
Date: 05/14/2019 02:35 PM
Subject: [EXTERNAL] Re: JES2 shutdown failure
Sent by: IBM Mainframe Discussion List 

init's drained?   lines drained? omvs shutdown?

On 5/14/19 5:32 PM, Tony Thigpen wrote:

I am testing on a DR box, and I am seeing a shutdown problem with JES2.

Here is the console log:
$da
$HASP612 NO ACTIVE JOBS
$P JES2
IEA964I HARDCOPY SUSPENDED, REASON=HCSW
$da
IEE707I $DA  NOT EXECUTED
D A,L
 JOBS M/S    TS USERS    SYSAS    INITS   ACTIVE/MAX VTAM

OAS

    0    2    0  00025    0    0/0

1

 JES2 JES2 IEFPROC  NSW  S  SHUTHUP1 SHUTHUP1 COMAND00 OWT

S


At this point, JES2 never seems to shut down. (The only job running is
SHUTHUP1 which is the automated shutdown procedure that runs outside
of JES2.)

Thoughts?


--
Brian W. France
Systems Administrator (Mainframe)
Pennsylvania State University
Administrative Information Services - Infrastructure/SYSARC
Rm 25 Shields Bldg., University Park, Pa. 16802
814-863-4739
b...@psu.edu

"To make an apple pie from scratch, you must first invent the universe."

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN



--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN




--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN




--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN