michelbutz wrote:
>I am getting a 047 abend running a program
>That runs in production
>The 047 abend under both TSO TEST and debug tool happens with a STC
>instruction which tries to
>Modify the 2 lengths of a AP instruction
>The program is NOT re-entrant
After reading all those replies, I'
This is embarrassing but I have to admit I don't have a clue what I did, and
more importantly, how to back out.
In SDSF's hold panel, I suddenly see one line for each output group (i.e.
SYSOUT DD) for all of my jobs (well at least for this prefix setting). I don't
see this woth other prefix se
Hi Peter
Any chance of a screen print/trap to show this phenomena?
/Steve
From: Peter Hunkeler
To: IBM-MAIN@LISTSERV.UA.EDU
Date: 2015-07-27 12:53
Subject:How comes SDSF HOLD panel shows one line per OutputGroup
instead of per job?
Sent by:IBM Mainframe Discussion List
Peter Hunkeler wrote:
>This is embarrassing but I have to admit I don't have a clue what I did, and
>more importantly, how to back out.
No, it is common. Don't stress. ;-)
>In SDSF's hold panel, I suddenly see one line for each output group (i.e.
>SYSOUT DD) for all of my jobs (well at least f
>Any chance of a screen print/trap to show this phenomena?
Yes, I could, but further investigation revealed that somehow the sysout dds
for the jobs in question were somehow split into separate JES2 output groups.
So it is obvious now, why each SYSOUT is display on a line of its own: They're
Another things I forgot - please show us your FILTER, DEST, SYSNAME, INPUT
(command), etc.?
Groete / Greetings
Elardus Engelbrecht
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listse
Solved! It was SMP/E who fooled me. I'm sorry to not have recognized this
before posting.
I had an SMP/E job doing some LIST processing for one zone. All DDs except from
the CSI were dynamically allocated. I repeated the LIST statement in the same
step to list from some more zones. SMP/E allocat
On Mon, 27 Jul 2015 00:13:03 -0500, Andy Wood wrote:
>On Wed, 22 Jul 2015 22:39:58 -0400, michelbutz wrote:
>
>>I am getting a 047 abend running a program
>>That runs in production
>>The 047 abend under both TSO TEST and debug tool happens with a STC
>>instruction which tries to
>>Modify the
The multiple output groups are caused when you do a SET BOUNDARY within a step.
If you use a different step for each SET BOUNDARY, then a single output entry
appears for the job.
Bob Longabaugh
CA Technologies
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@L
>The multiple output groups are caused when you do a SET BOUNDARY within a
>step. If you use a different step for each SET BOUNDARY, then a single output
>entry appears for the job.
Yep, this is what I did: multiple lists each for a different zone. I added DD
statements to this job for the
10 matches
Mail list logo
