Re: Health Checker startup

2006-11-13 Thread Greg Shirey
Barbara,

No, I didn't try that, I hadn't thought of it.  It sounded like an
interesting experiment, so I did - experiment, that is.  

I had wondered if it might bypass the search of the MSTJCL DD concatenations
and instead locate the proc found in our private proclib, but it didn't.  

Thanks,
Greg

-Original Message-
From: IBM Mainframe Discussion List On Behalf Of Barbara Nitz
Sent: Monday, November 13, 2006 1:22 AM

Greg,

have you tried starting health checker explicitly using this command:
S HZSPROC,SUB=JES2?
-
 


As of January 1, 2007, Ben E. Keith Company will no longer accept emails
addressed to our "bekco.com" address. Please change your information for
all Ben E. Keith contacts to our new email address, "benekeith.com". 
Thank you.


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


Re: Health Checker startup

2006-11-13 Thread Greg Shirey
>-Original Message-
>From: IBM Mainframe Discussion List On Behalf Of Shmuel Metz (Seymour J.)
>Sent: Sunday, November 12, 2006 12:47 PM

>Given that HZSPROC defines and calls an instream proc named HZSPROC,
>why are you surprised to receive the message PROCEDURE HZSPROC WAS
>EXPANDED USING INSTREAM PROCEDURE DEFINITION?

My surprise came from the fact that the proc being expanded was not the one
I'd modified and removed the job card (and PROC & PEND statements) from.
Sorry if my surprise seemed unwarranted to you, but I was having trouble
deciphering what I was reading in the fine manuals about "started task
processing", so I asked the members of the list for help.  

There has been discussion on the list about what to do to code a "started
job," but I didn't realize that HZSPROC was coded as one because the fine
manual doesn't use the term.  I later Googled for "started jobs" at ibm.com
and got only three hits -- apparently the term, while descriptive, is slang.

   
But it's all clear to me in hindsight. 

Greg Shirey
Ben E. Keith Company 


As of January 1, 2007, Ben E. Keith Company will no longer accept emails
addressed to our "bekco.com" address. Please change your information for
all Ben E. Keith contacts to our new email address, "benekeith.com". 
Thank you.


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


Re: Health Checker startup

2006-11-12 Thread Barbara Nitz
Greg,

have you tried starting health checker explicitly using this command:
S HZSPROC,SUB=JES2?
-
At one time I had this baffling JCL error (procedure not found) for an STC that 
was started previously without any problems. It turned out that that STC was 
also a subsystem, and there is a very old apar that states that everything 
building a subsystem is implicitly started sub=mstr unless during the first 
start this bit is set that indicates that it should be started sub=jes2. In 
other words, the first start command is sub=jes2, all subsequent steps are 
sub=mstr unless software set the bit.
-
We run the health checker, and I did not see a subsystem name that sounds like 
health checker, but we are zos 1.6, and things may have changed with 1.7.
Regards, Barbara Nitz
-- 
"Ein Herz für Kinder" - Ihre Spende hilft! Aktion: www.deutschlandsegelt.de
Unser Dankeschön: Ihr Name auf dem Segel der 1. deutschen America's Cup-Yacht!

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


Re: Health Checker startup

2006-11-12 Thread Shmuel Metz (Seymour J.)
In <[EMAIL PROTECTED]>, on 11/10/2006
   at 08:06 AM, Greg Shirey <[EMAIL PROTECTED]> said:

>Yes,

Given that HZSPROC defines and calls an instream proc named HZSPROC,
why are you surprised to receive the message PROCEDURE HZSPROC WAS
EXPANDED USING INSTREAM PROCEDURE DEFINITION?

>//HZSPROC  PROC HZSPRM='00'
>//HZSSTEP  EXEC   PGM=HZSINIT,REGION=0K,TIME=NOLIMIT,
>//  PARM='SET PARMLIB=&HZSPRM' 
>//HZSPDATA DD   DSN=SYS1.CPAC.HZSPDATA,DISP=OLD
>//PEND

That defines the instream proc.

>//EXEC HZSPROC

That calls it.
 
-- 
 Shmuel (Seymour J.) Metz, SysProg and JOAT
 ISO position; see  
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


Re: Health Checker startup

2006-11-10 Thread Greg Shirey
>-Original Message-
>From: IBM Mainframe Discussion List On Behalf Of Shmuel Metz (Seymour J.)
>Sent: Thursday, November 09, 2006 4:24 PM

>What is your Master JCL, 

There is no IEFJOBS DD and the IEFPDSI concatenation is 3 PDS's -
SYS1.PROCLIB, CPAC.PROCLIB, SYS1.IBM.PROCLIB.

>was the START under Master, 

No.

>is there a PROC statement in the member?
 
Yes, here it is, minus comments: 

//HZSPROC JOB JESLOG=SUPPRESS
//HZSPROC  PROC HZSPRM='00'
//HZSSTEP  EXEC   PGM=HZSINIT,REGION=0K,TIME=NOLIMIT,  
//  PARM='SET PARMLIB=&HZSPRM' 
//HZSPDATA DD   DSN=SYS1.CPAC.HZSPDATA,DISP=OLD
//PEND 
//EXEC HZSPROC 

Greg Shirey
Ben E. Keith Company


As of January 1, 2007, Ben E. Keith Company will no longer accept emails
addressed to our "bekco.com" address. Please change your information for
all Ben E. Keith contacts to our new email address, "benekeith.com". 
Thank you.


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


Re: Health Checker startup

2006-11-10 Thread Shmuel Metz (Seymour J.)
In <[EMAIL PROTECTED]>, on 11/06/2006
   at 10:52 AM, Greg Shirey <[EMAIL PROTECTED]> said:

>What do you mean by "precedence over IEFPDSI"?  The member was found
>in IEFPDSI.

What is your Master JCL, was the START under Master, is there a PROC
statement in the member?
 
-- 
 Shmuel (Seymour J.) Metz, SysProg and JOAT
 ISO position; see  
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


Re: Health Checker startup

2006-11-06 Thread Greg Shirey
>-Original Message-
>From: IBM Mainframe Discussion List On Behalf Of Walt Farrell
>Sent: Monday, November 06, 2006 12:09 PM

>>  
>> What do you mean by "precedence over IEFPDSI"?  The member was found in
>> IEFPDSI.
>>

>Are you sure it wasn't found in IEFJOBS rather than IEFPDSI?

Fairly sure - we have no IEFJOBS DD in MSTJCL00.  

Thanks,
Greg Shirey
Ben E. Keith Company


As of January 1, 2007, Ben E. Keith Company will no longer accept emails
addressed to our "bekco.com" address. Please change your information for
all Ben E. Keith contacts to our new email address, "benekeith.com". 
Thank you.


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


Re: Health Checker startup

2006-11-06 Thread Walt Farrell

On 11/6/2006 11:52 AM, Greg Shirey wrote:

-Original Message-
From: IBM Mainframe Discussion List On Behalf Of Shmuel Metz (Seymour J.)
Sent: Friday, November 03, 2006 2:00 PM



You have an instream proc in your JCL, and that takes precedence over

IEFPDSI.
 
What do you mean by "precedence over IEFPDSI"?  The member was found in

IEFPDSI.



Are you sure it wasn't found in IEFJOBS rather than IEFPDSI?

Walt

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


Re: Health Checker startup

2006-11-06 Thread Greg Shirey
>-Original Message-
>From: IBM Mainframe Discussion List On Behalf Of Shmuel Metz (Seymour J.)
>Sent: Friday, November 03, 2006 2:00 PM

>You have an instream proc in your JCL, and that takes precedence over
IEFPDSI.
 
What do you mean by "precedence over IEFPDSI"?  The member was found in
IEFPDSI.

Greg Shirey
Ben E. Keith Company  


As of January 1, 2007, Ben E. Keith Company will no longer accept emails
addressed to our "bekco.com" address. Please change your information for
all Ben E. Keith contacts to our new email address, "benekeith.com". 
Thank you.


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


Re: Health Checker startup

2006-11-03 Thread Shmuel Metz (Seymour J.)
In <[EMAIL PROTECTED]>, on 11/02/2006
   at 10:31 AM, Greg Shirey <[EMAIL PROTECTED]> said:

>When I started HZSPROC again, I was surprised to see no changes. 
>Message IEFC001I stated: 
>PROCEDURE HZSPROC WAS EXPANDED USING INSTREAM PROCEDURE DEFINITION

You have an instream proc in your JCL, and that takes precedence over
IEFPDSI.
 
-- 
 Shmuel (Seymour J.) Metz, SysProg and JOAT
 ISO position; see  
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


Re: Health Checker startup

2006-11-02 Thread Greg Shirey
It does indeed, and CPAC.PROCLIB is in our IEFPDSI, as you suggest.  

This is from MVS Init & Tuna Ref:

"When you start a started task, the system determines whether the START
command refers to a procedure or a job. (The system validates that the
IEFJOBS DD exists within the MSTJCLxx member.) If the IEFJOBS DD exists, the
system searches the IEFJOBS DD concatenation for the member requested in the
START command. If there is no member by that name in the IEFJOBS
concatenation, or if the IEFJOBS concatenation does not exist, the system
searches the IEFPDSI DD for the member requested in the START command. 

If a member is found, the system examines the first record for a valid JOB
statement and, if one exists, uses the member as the JCL source for the
started task. 

If the member does not have a valid JOB statement in its first record, the
system assumes that the source JCL is a procedure and creates JCL to invoke
the procedure. After JCL source has been created (or found), the system
processes the JCL."

The process described for locating a started job seems clear, but if the
member located does *not* have a JOB card in it, the manual is less than
clear to me what is supposed to transpire.  It says it will invoke the
procedure -- the one it found in the IEFPDSI concatenation?  Apparently not,
from the way my system behaves.  Is it just me, or does this need an RCF?   

Thanks,
Greg Shirey
Ben E. Keith Company 


-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf
Of Choate, Bill
Sent: Thursday, November 02, 2006 10:51 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: Health Checker startup

It sounds like CPAC.PROCLIB is included in your MSTJCLxx member under
the IEFJOBS DD and Health Checker is running as a started job from
there.


As of January 1, 2007, Ben E. Keith Company will no longer accept emails
addressed to our "bekco.com" address. Please change your information for
all Ben E. Keith contacts to our new email address, "benekeith.com". 
Thank you.


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


Re: Health Checker startup

2006-11-02 Thread Choate, Bill
It sounds like CPAC.PROCLIB is included in your MSTJCLxx member under
the IEFJOBS DD and Health Checker is running as a started job from
there.

Bill Choate
Emory University
AAIT

-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Greg Shirey
Sent: Thursday, November 02, 2006 11:31 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Health Checker startup

I've started working with the Health Checker on our z/OS 1.7 system and
encountered something that confused me, and I haven't found a clear
answer
in the Fine Manuals, so I turn to the collective wisdom of the List.  

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


Health Checker startup

2006-11-02 Thread Greg Shirey
I've started working with the Health Checker on our z/OS 1.7 system and
encountered something that confused me, and I haven't found a clear answer
in the Fine Manuals, so I turn to the collective wisdom of the List.  

After starting and stopping the Health Checker a few times to see what it
did by default, I needed to customize a few things, so I copied the supplied
HZSPROC proc from CPAC.PROCLIB into our SYS2.PROCLIB.ZOSR17 (which is first
in our JES2 PROC00 concatenation - CPAC.PROCLIB is third) and modified the
HZSPDATA DD and changed "HZSPRM=00" to "HZSPRM='(00,01)'".  

When I started HZSPROC again, I was surprised to see no changes.  Message
IEFC001I stated: 
PROCEDURE HZSPROC WAS EXPANDED USING INSTREAM PROCEDURE DEFINITION

Eh?  What?  Huh?  I at least expected to see that the proc had been expanded
from a PDS, not "instream".  This behavior is new to me.  

It seemed as though the proc was being read from CPAC.PROCLIB, so I renamed
it there, and the next time I issued "S HZSPROC", I got what I expected -
message IEFC001I stated the proc was expanded from my proc library.  But if
I rename the member in CPAC.PROCLIB back to HZSPROC and issue "S HZSPROC"
again, I get the original behavior - the proc is expanded using instream
procedure definition.  

The unusual thing about HZSPROC (at least to me) is that it has a JOB card
in it -- as the HC User's Guide says: "Note that although this looks like a
batch job it is a started task." -- but that doesn't indicate the system
would bypass the first HZSPROC member found in the PROC00 concatenation and
read a different one, does it?  For our testing purposes, I had taken the
JOB card out of "our" HZSPROC and the JESLOG=SUPPRESS so we could view all
the JESLOG messages.  

I'd appreciate any insight, if anyone has any.

TIA,
Greg Shirey
Ben E. Keith Company  

 


As of January 1, 2007, Ben E. Keith Company will no longer accept emails
addressed to our "bekco.com" address. Please change your information for
all Ben E. Keith contacts to our new email address, "benekeith.com". 
Thank you.


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html