MVSFORUMS.com :: View topic - Accessing a SYSOUT file without SDSF

through

[^/[Print]\]
Goto page 1, 2 Next :| |:
MVSFORUMS.com -> Problem Determination

#1: Accessing a SYSOUT file without SDSF Author: asr2, Location: Germany

Posted: Tue Jul 26, 2011 4:11 am
—
Is there any easy way of obtaining a SYSOUT file without using SDSF?
My problem: I need to analyze the content of a SYSOUT file for the current job (this is related to my previous question concerning the step completion code - after determining, for example, that a step failed, I need to find the reason). The DSNAME provided in the SCT is not valid (the last qualifier is ?).
The solutions I have considered are not very satisfactory:
1. Rather than using SYSOUT, I can write the output to a file.
2. I can use TSO OUTPUT to write the complete output to a file.
3. I could possibly use special output classes for such SYSOUTs, but I do not necessarily know what classes are available.

Have I overlooked some obvious solution? I do not have SDSF available.

#2: Author: expat, Location: Welsh Wales

Posted: Tue Jul 26, 2011 4:59 am
—
Surely another product which does the same as SDSF

#3: Author: asr2, Location: Germany

Posted: Tue Jul 26, 2011 6:46 am
—
That would be too easy and the fourth solution that I did not mention. I actually would like a native z/OS solution that is not dependent on any other (third-party) product. SDSF is an "overkill" for most application programmers.

#4: Author: superk,

Posted: Tue Jul 26, 2011 9:48 am
—
If you review the description of the TSO SUBMIT command in the manual, they have this little tidbit of information:

Quote:

SUBMIT is a foreground-initiated-background (FIB) command. You must be authorized by installation management to use SUBMIT. This command is generally used in conjunction with the CANCEL, STATUS, and OUTPUT commands.

so hopefully that answers your question.

#5: Author: papadi,

Posted: Tue Jul 26, 2011 1:41 pm
—

Quote:

SDSF is an "overkill" for most application programmers.

Opinions vary. . . Wink

#6: Author: Anuj Dhawan, Location: Mumbai,India

Posted: Sat Jul 30, 2011 11:44 am
—
Check out Lionel B. Dyck he has a great little tool, SDFSEXT, a generalized SDSF batch tool to extract all or part of your sysout into a dataset that you could do whatever you want with.

#7: Author: asr2, Location: Germany

Posted: Sat Jul 30, 2011 11:44 pm
—
Anuj

Thanks. SDSFEXT is actually very similar to a procedure that I developed for RDz. But, judging by name, SDSF Extract, requires the availability of SDSF. Fortunately, the most important JES files (JESMSGLG, JESJCL, ...) are available without SDSF.

Regards
Tony

#8: Author: asr2, Location: Germany

Posted: Sun Aug 14, 2011 7:46 am
—
While I was looking for a solution for a different problem, I found the solution for Idea

this problem, namely, with the JEST Spool Data set Browser, described, more or less, in the JES Application Programming manual. Implementing the solution was not helped by lack of documentation, for example, the DALUASSR text unit was not described in the MVS Programming: Authorized Assembler Services Guide for z/OS 1.11.

Tony

#9: Author: warp5, Location: Germany

Posted: Mon Aug 15, 2011 1:46 am
—
asr2, please post more information, this might be of interest for many people.

#10: Author: Anuj Dhawan, Location: Mumbai,India

Posted: Mon Aug 15, 2011 8:04 am
—

warp5 wrote:

asr2, please post more information, this might be of interest for many people.

Yes, I agree - please do so.

#11: Author: kolusu, Location: San Jose

Posted: Mon Aug 15, 2011 10:26 am
—
warp5, Anuj Dhawan,

I think asr2 is talking about spool browse in JES3 . If you are a JES3 user then may be the following links will help you understand it better.

JES3 Spool Browse

JES Spool Data Set Browse from Application programming guide

Kolusu

#12: Author: asr2, Location: Germany

Posted: Mon Aug 15, 2011 11:24 pm
—
I am running on a JES2 system. The second link does provide the basic data which together with the MVS Authorized Assembler System Services for z/OS 1.12 (Dynamic Allocation) suffices to browse a spool file.

Tony

#13: Author: Anuj Dhawan, Location: Mumbai,India

Posted: Wed Aug 17, 2011 5:56 am
—
Thanks Kolusu and Tony.

Have a good one,

#14: Author: asr2, Location: Germany

Posted: Mon Aug 22, 2011 10:41 am
—
The solution I described is only half a solution, because the described technique can only be used for the current job. What I also need is a simple JES navigation; list the held jobs, select a job, and then select a DDname. I looked at the code for QUEUE, which does this but a lot more besides and so it is difficult to determine what I actually need for my task.

The only documentation I can find for JES programming describes EXITs, customisation, etc., but not my task. Have I overlooked something?

Regards
Tony

#15: Author: nevilh,

Posted: Mon Aug 22, 2011 12:16 pm
—
Have you tried taking a look at the JES2 SAPI (SSI) this should provide you with what you want

MVSFORUMS.com -> Problem Determination

output generated using printer-friendly topic mod. All times are GMT - 5 Hours

Goto page 1, 2 Next :| |: Page 1 of 2