On Sun, 2006-03-19 at 10:58 -0500, Peter Relson wrote:
There already is a health checker check that reports on the number of CADS
in use compared to the number that were defined via MAXCADS.
Sam has been kicking this drum for a while. With Bob and Peter nudging
me I (finally) decided to
There already is a health checker check that reports on the number of CADS
in use compared to the number that were defined via MAXCADS.
Peter Relson
z/OS Core Technology Design
--
For IBM-MAIN subscribe / signoff / archive
In a message dated 3/19/2006 9:59:09 A.M. Central Standard Time,
[EMAIL PROTECTED] writes:
There already is a health checker check that reports on the number of CADS
in use compared to the number that were defined via MAXCADS.
Right, just couldn't get it to point at target parmlib
PM
To: 'IBM Mainframe Discussion List'
Subject:FW: FFST Abend at Startup
-Original Message-
From: Miller, Pat
Sent: Monday, January 16, 2006 10:40 AM
To: 'Ulrich Krueger '
Subject:RE: FFST Abend at Startup
I am using all the defaults as it comes
In a message dated 3/18/2006 2:44:44 P.M. Central Standard Time,
[EMAIL PROTECTED] writes:
In case anybody else could use this: FFST cc=16 at startup with no
definitive messages likely means that you need to bump up MAXCAD in
IEASYSxx. What the @#$% is MAXCAD, you ask? Allow me to quote
On Sat, 2006-03-18 at 14:44 -0600, Miller, Pat wrote:
What the @#$% is MAXCAD, you ask? Allow me to quote INIT
TUNING: ... the number of entries available for SCOPE=COMMON data spaces
on all primary address space access lists. Glad we cleared that up.
MAXCAD is another recurring theme
-Original Message-
From: Miller, Pat
Sent: Monday, January 16, 2006 10:40 AM
To: 'Ulrich Krueger '
Subject:RE: FFST Abend at Startup
I am using all the defaults as it comes with ServerPac. EPWPARM was empty.
The PROC comes with the SYSABEND DD SYSOUT=A. I was surprised
Shmuel Metz (Seymour J.) wrote:
In [EMAIL PROTECTED], on
01/13/2006
at 01:44 PM, Miller, Pat [EMAIL PROTECTED] said:
I'm getting the following when EPWFFST starts up under z/OS 1.4:
1. Are you starting EPWFFST under JES3 or under MSTR?
$HASP708 EPWFFST OPEN FAILED
In [EMAIL PROTECTED], on
01/13/2006
at 01:44 PM, Miller, Pat [EMAIL PROTECTED] said:
I'm getting the following when EPWFFST starts up under z/OS 1.4:
1. Are you starting EPWFFST under JES3 or under MSTR?
2. How is SYSABEND defined?
3. Why SYSABEND instead of SYSMDUMP?
--
Shmuel
I'm getting the following when EPWFFST starts up under z/OS 1.4:
EPW0051I FFSTFFDC: INITIALIZATION OF FFST/FFDC COMPLETE
EPW0201I EPWFFST: INITIALIZATION OF FFST/ESA IN PROGRESS
EPW0504I EPWFFST: FFSTPARM MEMBER START00 READ SUCCESSFULLY
$HASP708 EPWFFST OPEN
II07553?
Yes, it talks about DB2PM, but perhaps the same pitfall awaits FFST if you
start the task with the same name as the subsystem name.
Brian
On Fri, 13 Jan 2006 13:44:49 -0600, Miller, Pat
[EMAIL PROTECTED] wrote:
I'm getting the following when EPWFFST starts up under z/OS 1.4:
EPW0051I
Pat,
It may not help much but for what it is worth we have FFST running fine
on both z/OS R4 R6.
$HASP373 EPWFFST STARTED
IEF403I EPWFFST - STARTED
EPW0051I FFSTFFDC: INITIALIZATION OF FFST/FFDC COMPLETE
EPW0201I EPWFFST: INITIALIZATION OF FFST/ESA IN PROGRESS
I get 0 hits on this on IBMLINK.
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Brian Peterson
Sent: Friday, January 13, 2006 1:53 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject:Re: FFST Abend at Startup
II07553?
Yes, it talks about
-Original Message-
From: IBM Mainframe Discussion List
[mailto:[EMAIL PROTECTED] On Behalf Of Lizette Koehler
Sent: Friday, January 13, 2006 2:30 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: FFST Abend at Startup
Pat,
My thought is that the SYSABEND DD is what caused the problem
List [mailto:[EMAIL PROTECTED] On
Behalf Of Ulrich Krueger
Sent: Friday, January 13, 2006 3:33 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject:Re: FFST Abend at Startup
Pat,
FFST during IPL is usually started with an internally issued S
EPWFFST.FFST,SUB=MSTR
Unless I'm mistaken, a started task
Pat,
You can create a dummy member called EPWHWR01 (hardware probes) by just
editing a member and put a * in column 1 (that is the comment card) and save
it.
Then try restarting FFST again.
Lizette Koehler
--
For IBM-MAIN
Pat,
are you trying to customize FFST?
My EPWPARM dataset is completely empty. There's not even a START00 (default)
member.
I suspect that you have a syntax error in START00
If you need to get FFST up and running, try an empty EPWPARM dataset, so you're
using all the defaults.
Anything after
17 matches
Mail list logo