Our shop had migrated to z/os 1.7 from z/OS 1.4.
After migration one of our production job is abending with S30A-10
abend during freemain and subsequently the job encounters another
abend S878-18 (with z/OS 1.7).
When we resubmitted the same job in another two different LPAR that
has
I haven't code ACS routines in years.
Does anybody know where to find a reference on how to do it?
-
Too busy driving to stop for gas!
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL
There are several possibilities as noted in the 30A-10 abend and the 878 abend
but since it seems to be occurring only in 1.7, I would first check that the
Getmain or Storage request executed successfully in 1.7 and that the address of
the area acquired as well as it's length was saved properly
http://publibz.boulder.ibm.com/epubs/pdf/dgt2c750.pdf
Date: Sun, 30 Dec 2007 11:41:01 +
From: [EMAIL PROTECTED]
Subject: SMS ACS Routine Coding
To: IBM-MAIN@BAMA.UA.EDU
I haven't code ACS routines in years.
Does anybody know where to find a reference on how to do it?
-
Too busy
Why do so many senior managers seem so know-it-all-ish??
Dunno. Maybe for the same reason as senior techies. You know,
like the ones that specifically remember things that never existed.
Date: Sat, 29 Dec 2007 11:02:45 -0600
From: [EMAIL PROTECTED]
Subject: Re: Curiousity question:
Ted,
There are three presentations on SHARE.ORG on Coding and Debugging ACS
routines. This was presented by DTS Software.
One thing to watch out for is the ACS source code must be unnum'd. Otherwise
you get a strange error that makes no sense.
Lizette
I haven't code ACS routines in
In [EMAIL PROTECTED], on 12/28/2007
at 07:26 PM, Doug Fuerst [EMAIL PROTECTED] said:
Maybe Apple will patent air next. They can join Microsoft in the
application. This is insane.
It's certainly abusive if apple means to enforce the patent, but if it's
just a defensive patent then it's a
---snip---
IIRC, SYS1.NULLFILE was recognized by the system as a special case of
DUMMY. But it filled in the DSNAME field of the JFCB.
You are thinking of DSN=NULLFILE. Now we also have PATH=/dev/null.
Try looking at the DF/SMSdfp Storage Admin Guide and the Reference
Manual. The reference manual has the actual coding stuff in there.
Doug
At 09:52 30-12-07, you wrote:
Ted,
There are three presentations on SHARE.ORG on Coding and Debugging
ACS routines. This was presented by DTS Software.
On Fri, 28 Dec 2007 18:46:05 -0800, Paul Knudsen
[EMAIL PROTECTED] wrote:
Judicious use of DISPLAY statements can tell the programmer, for example,
exactly which record to pull from the input file. Yes, you can also figure
that out from the dump, but it takes longer.
Don't you have a debugger,
Howard:
You bring up a very good point. I was thinking as I followed this thread, that
when I supported a large group of Cobol programmers that all of the posters
thus far had a valid point. At one point we too said there was no need to use
the display, or something we saw once in a while,
On Fri, 28 Dec 2007 18:46:05 -0800, Paul Knudsen
[EMAIL PROTECTED] wrote:
Judicious use of DISPLAY statements can tell the programmer, for
example,
exactly which record to pull from the input file. Yes, you can also
figure
that out from the dump, but it takes longer.
Don't you have a
At 09:39 + on 12/29/2007, Phil Payne wrote about It keeps getting uglier:
Some agencies (governments, defence departments, etc.) require
vendors to supply FULL documentationn on any products delivered. IMO
that would include the trade secret stuff. Someone needs to find a
jurisdiction
On Dec 30, 2007, at 8:52 AM, Lizette Koehler wrote:
Ted,
There are three presentations on SHARE.ORG on Coding and Debugging
ACS routines. This was presented by DTS Software.
One thing to watch out for is the ACS source code must be unnum'd.
Otherwise you get a strange error that makes
DoD, etc., has such requirements, but there is always an NDA in effect, and
the identities of those persons having access to the materials subject to
the NDA are clearly spelled out, as are the penalties for any disclosure of
the contents thereof.
The FOIA specifically excludes trade secrets and
On Dec 30, 2007, at 4:03 PM, Bill Wilkie wrote:
Howard:
You bring up a very good point. I was thinking as I followed this
thread, that when I supported a large group of Cobol programmers
that all of the posters thus far had a valid point. At one point we
too said there was no need to use
In [EMAIL PROTECTED], on 12/28/2007
at 06:52 AM, Barbara Nitz [EMAIL PROTECTED] said:
Actually, I just had a bloody row about a DD dummy statement in the JCL
for a new release of a vendor product. It appears that a dd dummy
generates a dsn of NULLFILE in the JFCB
DSN=NULLFILE has been
In [EMAIL PROTECTED], on 12/27/2007
at 11:16 PM, Doug Fuerst [EMAIL PROTECTED] said:
You bet Ed. I learned things about diagnose that I never saw written
down
Perhaps you looked in the wrong places.
--
Shmuel (Seymour J.) Metz, SysProg and JOAT
ISO position; see
In [EMAIL PROTECTED], on 12/28/2007
at 03:55 PM, Paul Gilmartin [EMAIL PROTECTED] said:
Which was a grievous and irresponsible and unnecessary design blunder.
No.
Who benefits from this special treatment of PATH=/dev/null?
What special treatment?
It only adds confusion by making the
In [EMAIL PROTECTED], on 12/28/2007
at 10:10 AM, Rick Fochtman [EMAIL PROTECTED] said:
The most basic description was present, but all it really said was
machine dependant.
That's really all that they could say, except for the caveats.
I, for one, would like to see more detail,
Be careful
In [EMAIL PROTECTED], on 12/27/2007
at 09:53 PM, Ed Gould [EMAIL PROTECTED] said:
I could be wrong but I think he is talking about the undocumented
option codes that a diagnose could *really* do.
There may be many such on current processors, but can you cite any in the
1960's?
--
To the people who did not like the high CPU utilization in MFNetDisk. The bug
is over!
Try it again.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET
On Dec 30, 2007, at 7:58 PM, Shmuel Metz (Seymour J.) wrote:
In [EMAIL PROTECTED], on 12/27/2007
at 09:53 PM, Ed Gould [EMAIL PROTECTED] said:
I could be wrong but I think he is talking about the undocumented
option codes that a diagnose could *really* do.
There may be many such on
I don't think so.
Unless of course the Senior IBM factory reps didn't know either.
I think they knew where to look.
Doug
Snip
Perhaps you looked in the wrong places.
--
Shmuel (Seymour J.) Metz, SysProg and JOAT
Doug Fuerst
Consultant
BK Associates
Brooklyn, NY
(718) 921-2620 (Office)
24 matches
Mail list logo
