Message-
From: William Walsh
Sent: 06 December 2005 15:01
To: 'IBM Mainframe Discussion List'
Subject: START fails no diagnostics!
Have you ever seen a situation where the START command is issued, but the
address space fails with no diagnostics:
05340 13:30:58.39 WWALSH 0290 START
BBO6ACR
In
[EMAIL PROTECTED],
on 12/06/2005
at 03:00 PM, William Walsh [EMAIL PROTECTED] said:
Have you ever seen a situation where the START command is issued, but
the address space fails with no diagnostics:
No. How would I know that it had failed without a message to that
effect?
05340
On Tue, 6 Dec 2005 15:00:51 -, William Walsh
[EMAIL PROTECTED] wrote:
Have you ever seen a situation where the START command is issued, but the
address space fails with no diagnostics:
05340 13:30:58.39 WWALSH 0290 START
BBO6ACR,JOBNAME=BBOS001,ENV=CPAC.CPAC.BBOS001
05340 13:30:58.44
Have you ever seen a situation where the START command is issued, but the
address space fails with no diagnostics:
05340 13:30:58.39 WWALSH 0290 START
BBO6ACR,JOBNAME=BBOS001,ENV=CPAC.CPAC.BBOS001
05340 13:30:58.44 0090 IRR812I PROFILE BBO6ACR.* (G) IN
-Original Message-
From: IBM Mainframe Discussion List
[mailto:[EMAIL PROTECTED] On Behalf Of William Walsh
Sent: Tuesday, December 06, 2005 9:01 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: START fails no diagnostics!
Have you ever seen a situation where the START command is
issued
In a message dated 12/6/2005 9:12:29 A.M. Central Standard Time,
[EMAIL PROTECTED] writes:
Any ideas?
Probably need to look down the syslog and see if BBOS01 is
purged. Default sysout for STC could be set to a PURGE class.
So if you've got access to JCL change SYSOUT=* to SYSOUT=H
or
Of
William Walsh
Sent: Tuesday, December 06, 2005 10:01 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: START fails no diagnostics!
Have you ever seen a situation where the START command is issued, but the
address space fails with no diagnostics:
05340 13:30:58.39 WWALSH 0290 START
BBO6ACR,JOBNAME=BBOS001
One thing I usually do with STCs that fail, is to run the STC JCL as a batch
job. It would not matter if the job failed, but I would be able to see if
there were any data sets that were not valid or if there were some other
issue or messages.
//TSTJCL JOB ...
//S1 EXEC
In a recent note, Lizette Koehler said:
Date: Tue, 6 Dec 2005 09:01:57 -0700
One thing I usually do with STCs that fail, is to run the STC JCL as a batch
job. It would not matter if the job failed, but I would be able to see if
there were any data sets that were not valid or if
On Tue, 6 Dec 2005 09:01:57 -0700, Lizette Koehler
[EMAIL PROTECTED] wrote:
One thing I usually do with STCs that fail, is to run the STC JCL as a
batch
job. ...
Another technique that has worked for me is to override MSGCLASS.
S whatever,MSGCLASS=x where x is your hold class. That will save
On Tue, 6 Dec 2005 11:30:53 -0700, Paul Gilmartin
[EMAIL PROTECTED] wrote:
...
This technique is far less effective if the STC JCL contains system
symbols. There's another good argument here for supporting symbols
in batch JCL.
...
For that kind of test it's a whole lot faster to stick some SET
In a recent note, Patrick O'Keefe said:
Date: Tue, 6 Dec 2005 14:18:55 -0600
On Tue, 6 Dec 2005 11:30:53 -0700, Paul Gilmartin
[log in to unmask] wrote:
This technique is far less effective if the STC JCL contains system
symbols. There's another good argument here for supporting
12 matches
Mail list logo
