Sorry, my bad. We too skipped 1.7. We have a bad habit of 'discovering' new
stuff that's actually been around for a while. Apologies for misleading those
on z/OS 1.7.
Regards,
Art Gutowski
Ford Motor Company
--
For IBM-MAIN
Bob Shannon wrote:
>We're current on 1.7 maintenance and we get the same response. It must
have been introduced in 1.8.
It is indeed introduced in 1.8.
Summary of changes for SA22-7526-07, z/OS Version 1 Release 8.
New information :
$ADD SRVCLASS
$D SRVCLASS
$T SRVCLASS
$S SRVCLASS
$P SRVC
> I was curious, too, so I entered $D JES2 on my z/OS 1.7 system and got
>the following:
>$HASP649 $DJES2INVALID COMMAND
We're current on 1.7 maintenance and we get the same response. It must have
been introduced in 1.8.
Bob Shannon
Rocket Software
--
I was curious, too, so I entered $D JES2 on my z/OS 1.7 system and got
the following:
$HASP649 $DJES2INVALID COMMAND
Greg Shirey
Ben E. Keith Co.
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of Mark Zelden
Sent: Wednesday, June 04
On Wed, 4 Jun 2008 07:15:14 -0500, Arthur Gutowski <[EMAIL PROTECTED]> wrote:
>We've found '$D JES2' (in z/OS 1.7?) quite useful for our automation scripts.
>If there's anything left, prompt the operator for assistance before proceeding
>with the $PJES2...
>
Did this exist in z/OS 1.7? We skippe
We've found '$D JES2' (in z/OS 1.7?) quite useful for our automation scripts.
If there's anything left, prompt the operator for assistance before proceeding
with the $PJES2...
Regards,
Art Gutowski
Ford Motor Company
[EMAIL PROTECTED]
---
Subject
.EDU> $PJES2 and Parallel Sysplex
06/03/2008 03:41
Yes, I was assuming an SFM policy was in effect. Why run without one??
>>> "Scott Rowe" <[EMAIL PROTECTED]> 6/3/2008 9:54:01 AM >>>
I hope you meant to say to issue the RESET CLEAR before replying DOWN!
You can eliminate this step in most cases with an SFM policy, which helps
eliminate poss
I hope you meant to say to issue the RESET CLEAR before replying DOWN!
You can eliminate this step in most cases with an SFM policy, which helps
eliminate possible human error.
>>> Richard Bond <[EMAIL PROTECTED]> 6/3/2008 8:18 AM >>>
Mike,
Don't issue the vary until JES2 (and everything els
Even here, a $PJES2,ABEND - "END" would be preferable. Then you could do he
"Z EOD".
>>> "Barbara Nitz" <[EMAIL PROTECTED]> 6/3/2008 7:20 AM >>>
>It just doesn't sound right to me. It would make more sense that JES2
>could shut itself down cleanly than just pulling the rug out from under
>i
Mike,
Don't issue the vary until JES2 (and everything else) is down and you've done a
"Z EOD" to clear various buffers (like SMF).
After the "vary offline" has completed be sure to issue a RESET CLEAR for that
system on the HMC.
You have been ill advised.
Dick
>>> "Mike Myers" <[EMAIL PROTEC
>It just doesn't sound right to me. It would make more sense that JES2
>could shut itself down cleanly than just pulling the rug out from under
>it by abruptly stopping XCF services before JES2 had a chance to clean
>up its act. So, I'm wondering if anyone else out there has heard this
>same st
Hi all:
I have had someone tell me yesterday that they have been told that when
shutting down a member in a parallel sysplex that once you get "ALL
AVAILABLE FUNCTIONS COMPLETE" from JES2 that you should then issue the V
XCF,member,OFFLINE command without first stopping JES2 ($PJES2). The
imp
13 matches
Mail list logo
