Re: GTF trace for a JCL error?

[Mike Schwab]

Our system had 7 days.

On Tue, Jan 30, 2024 at 12:57 PM Paul Gilmartin <
042bfe9c879d-dmarc-requ...@listserv.ua.edu> wrote:

> On Tue, 30 Jan 2024 14:41:59 +, Allan Staller  wrote:
> >
> >You need to look at the JES output to determine the error.
> >Use the following command
> >S taskname,,,MSGCLASS=x  where x is a held sysout class.
> >
> >HTH,
> >
> Wouldn't it be a good Idea to have a class for "Delete after one hour"!?
>
> I've often wanted that.
> --
> gil
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>


-- 
Mike A Schwab, Springfield IL USA
Where do Forest Rangers go to get away from it all?

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: GTF trace for a JCL error?

[Paul Gilmartin]

On Tue, 30 Jan 2024 14:41:59 +, Allan Staller  wrote:
>
>You need to look at the JES output to determine the error.
>Use the following command
>S taskname,,,MSGCLASS=x  where x is a held sysout class.
>
>HTH,
> 
Wouldn't it be a good Idea to have a class for "Delete after one hour"!?

I've often wanted that.
-- 
gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: GTF trace for a JCL error?

[Gibney, Dave]

Have (or create from sandbox) a simple/failsafe version of the VTAN proc.
Export the spool files and import into sandbox or other lpar.
I suspect there are sufficwnt breadcrumbs in a standalone dump.

Test changes to VTAM proc by running it via a job before you shutdown.

> -Original Message-
> From: IBM Mainframe Discussion List  On
> Behalf Of Peter Ten Eyck
> Sent: Tuesday, January 30, 2024 10:11 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: GTF trace for a JCL error?
> 
> [EXTERNAL EMAIL]
> 
> Dave,
> 
> It was VTAM that would not come up due to a JCL error. We could not sign on
> to that LPAR and access JES. I was researching if I could see the JCL error 
> via a
> GTF trace. Sounding like I will not be able to do that.
> 
> In this case, starting the VTAM STC again with S , SUB=MSTR would
> write the JCL error to the console.
> 
> The issue has been resolved, just researching what other methods I could have
> used…
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions, send email to
> lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: GTF trace for a JCL error?

[Peter Ten Eyck]

Dave,

It was VTAM that would not come up due to a JCL error. We could not sign on to 
that LPAR and access JES. I was researching if I could see the JCL error via a 
GTF trace. Sounding like I will not be able to do that.

In this case, starting the VTAM STC again with S , SUB=MSTR would write 
the JCL error to the console.

The issue has been resolved, just researching what other methods I could have 
used…

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: GTF trace for a JCL error?

[Gibney, Dave]

Run a job with //STEP EXEC procname

Presumably it will experience the same JCL error

> -Original Message-
> From: IBM Mainframe Discussion List  On
> Behalf Of Peter Ten Eyck
> Sent: Tuesday, January 30, 2024 6:31 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: GTF trace for a JCL error?
> 
> [EXTERNAL EMAIL]
> 
> Under z/OS 2.4.
> 
> I have a STC when started, fails with the following error in the SYSLOG:
> 
> IEE132I START COMMAND DEVICE ALLOCATION ERROR
> 
> Looking at the STC output in JES, there is a JCL error in the proc (dataset 
> not
> found).
> 
> Is there a way to "see" the JCL error without looking at the JES output?
> 
> I have been researching and running a GTF trace with no success "seeing" the
> JCL error, not sure what GTF trace options to turn on or if it is possible to 
> see
> that JCL error via a GTF trace.
> 
> Is it possible to see that JCL error in a GTF trace, if so, what options 
> (parms) do
> I need to run with?
> 
> 
> 
> Note: We had an issue with VTAM not coming up on a LPAR and we were
> unable to access JES to see the JCL error.
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: GTF trace for a JCL error?

[Peter Ten Eyck]

Thanks for the tip, in this case, S ,sub=MSTR works. As in, writes the 
IEFA107I JCL error to the console.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: GTF trace for a JCL error?

[Styles, Andy (CIO GS - Core Infrastructure & IT Operations )]

You're going to be a bit stuck without VTAM up. 

Does the proc in question live in a dataset allocated to IEFPDSI in MSTJCLxx? 
If so, you might be able to issue S proc,SUB=MSTR and see the corresponding 
IEF196I messages on the console.

Andy Styles

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Peter Ten Eyck
Sent: Tuesday, January 30, 2024 2:31 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: GTF trace for a JCL error?

[Some people who received this message don't often get email from 
04d3761a18a7-dmarc-requ...@listserv.ua.edu. Learn why this is important at 
https://aka.ms/LearnAboutSenderIdentification ]

*** This email is from an external source - be careful of attachments and 
links. Please report suspicious emails ***

Under z/OS 2.4.

I have a STC when started, fails with the following error in the SYSLOG:

IEE132I START COMMAND DEVICE ALLOCATION ERROR

Looking at the STC output in JES, there is a JCL error in the proc (dataset not 
found).

Is there a way to "see" the JCL error without looking at the JES output?

I have been researching and running a GTF trace with no success "seeing" the 
JCL error, not sure what GTF trace options to turn on or if it is possible to 
see that JCL error via a GTF trace.

Is it possible to see that JCL error in a GTF trace, if so, what options 
(parms) do I need to run with?



Note: We had an issue with VTAM not coming up on a LPAR and we were unable to 
access JES to see the JCL error.

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Lloyds Banking Group plc. Registered Office: The Mound, Edinburgh EH1 1YZ. 
Registered in Scotland no. SC95000. Telephone: 0131 225 4555.

Lloyds Bank plc. Registered Office: 25 Gresham Street, London EC2V 7HN. 
Registered in England and Wales no. 2065. Telephone 0207626 1500.

Bank of Scotland plc. Registered Office: The Mound, Edinburgh EH1 1YZ. 
Registered in Scotland no. SC327000. Telephone: 03457 801 801.

Lloyds Bank Corporate Markets plc. Registered office: 25 Gresham Street, London 
EC2V 7HN. Registered in England and Wales no. 10399850.

Scottish Widows Schroder Personal Wealth Limited. Registered Office: 25 Gresham 
Street, London EC2V 7HN. Registered in England and Wales no. 11722983.

Lloyds Bank plc, Bank of Scotland plc and Lloyds Bank Corporate Markets plc are 
authorised by the Prudential Regulation Authority and regulated by the 
Financial Conduct Authority and Prudential Regulation Authority.

Scottish Widows Schroder Personal Wealth Limited is authorised and regulated by 
the Financial Conduct Authority.

Lloyds Bank Corporate Markets Wertpapierhandelsbank GmbH is a wholly-owned 
subsidiary of Lloyds Bank Corporate Markets plc. Lloyds Bank Corporate Markets 
Wertpapierhandelsbank GmbH has its registered office at Thurn-und-Taxis Platz 
6, 60313 Frankfurt, Germany. The company is registered with the Amtsgericht 
Frankfurt am Main, HRB 111650. Lloyds Bank Corporate Markets 
Wertpapierhandelsbank GmbH is supervised by the Bundesanstalt für 
Finanzdienstleistungsaufsicht.

Halifax is a division of Bank of Scotland plc.

HBOS plc. Registered Office: The Mound, Edinburgh EH1 1YZ. Registered in 
Scotland no. SC218813.



This e-mail (including any attachments) is private and confidential and may 
contain privileged material. If you have received this e-mail in error, please 
notify the sender and delete it (including any attachments) immediately. You 
must not copy, distribute, disclose or use any of the information in it or any 
attachments. Telephone calls may be monitored or recorded.


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: GTF trace for a JCL error?

[Allan Staller]

Classification: Confidential

You need to look at the JES output to determine the error.
Use the following command
S taskname,,,MSGCLASS=x  where x is a held sysout class.

HTH,

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Ituriel do Neto
Sent: Tuesday, January 30, 2024 8:39 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: GTF trace for a JCL error?

[CAUTION: This Email is from outside the Organization. Unless you trust the 
sender, Don’t click links or open attachments as it may be a Phishing email, 
which can steal your Information and compromise your Computer.]

Hi,

You can check the jobclass definitions of your STCs by issuing 
$DJOBCLASS(STC),LONG or looking into SDSF at JC screen. Probably the outdisp is 
(PURGE,PURGE).

In this case, you may change it to (HOLD,HOLD) to see the JCL.


Best Regards

Ituriel do Nascimento Neto
z/OS System Programmer






Em terça-feira, 30 de janeiro de 2024 às 11:31:17 BRT, Peter Ten Eyck 
<04d3761a18a7-dmarc-requ...@listserv.ua.edu> escreveu:





Under z/OS 2.4.

I have a STC when started, fails with the following error in the SYSLOG:

IEE132I START COMMAND DEVICE ALLOCATION ERROR

Looking at the STC output in JES, there is a JCL error in the proc (dataset not 
found).

Is there a way to "see" the JCL error without looking at the JES output?

I have been researching and running a GTF trace with no success "seeing" the 
JCL error, not sure what GTF trace options to turn on or if it is possible to 
see that JCL error via a GTF trace.

Is it possible to see that JCL error in a GTF trace, if so, what options 
(parms) do I need to run with?



Note: We had an issue with VTAM not coming up on a LPAR and we were unable to 
access JES to see the JCL error.

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN
::DISCLAIMER::

The contents of this e-mail and any attachment(s) are confidential and intended 
for the named recipient(s) only. E-mail transmission is not guaranteed to be 
secure or error-free as information could be intercepted, corrupted, lost, 
destroyed, arrive late or incomplete, or may contain viruses in transmission. 
The e mail and its contents (with or without referred errors) shall therefore 
not attach any liability on the originator or HCL or its affiliates. Views or 
opinions, if any, presented in this email are solely those of the author and 
may not necessarily reflect the views or opinions of HCL or its affiliates. Any 
form of reproduction, dissemination, copying, disclosure, modification, 
distribution and / or publication of this message without the prior written 
consent of authorized representative of HCL is strictly prohibited. If you have 
received this email in error please delete it and notify the sender 
immediately. Before opening any email and/or attachments, please check them for 
viruses and other defects.


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: GTF trace for a JCL error?

[Ituriel do Neto]

Hi,

You can check the jobclass definitions of your STCs by issuing 
$DJOBCLASS(STC),LONG or looking into SDSF at JC screen. Probably the outdisp is 
(PURGE,PURGE).

In this case, you may change it to (HOLD,HOLD) to see the JCL.


Best Regards

Ituriel do Nascimento Neto
z/OS System Programmer






Em terça-feira, 30 de janeiro de 2024 às 11:31:17 BRT, Peter Ten Eyck 
<04d3761a18a7-dmarc-requ...@listserv.ua.edu> escreveu: 





Under z/OS 2.4.

I have a STC when started, fails with the following error in the SYSLOG:

IEE132I START COMMAND DEVICE ALLOCATION ERROR

Looking at the STC output in JES, there is a JCL error in the proc (dataset not 
found).

Is there a way to "see" the JCL error without looking at the JES output?

I have been researching and running a GTF trace with no success "seeing" the 
JCL error, not sure what GTF trace options to turn on or if it is possible to 
see that JCL error via a GTF trace.

Is it possible to see that JCL error in a GTF trace, if so, what options 
(parms) do I need to run with?



Note: We had an issue with VTAM not coming up on a LPAR and we were unable to 
access JES to see the JCL error.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: GTF trace for a JCL error?

[Allan Staller]

Classification: Confidential

Nope!

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Peter Ten Eyck
Sent: Tuesday, January 30, 2024 8:31 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: GTF trace for a JCL error?

[CAUTION: This Email is from outside the Organization. Unless you trust the 
sender, Don’t click links or open attachments as it may be a Phishing email, 
which can steal your Information and compromise your Computer.]

Under z/OS 2.4.

I have a STC when started, fails with the following error in the SYSLOG:

IEE132I START COMMAND DEVICE ALLOCATION ERROR

Looking at the STC output in JES, there is a JCL error in the proc (dataset not 
found).

Is there a way to "see" the JCL error without looking at the JES output?

I have been researching and running a GTF trace with no success "seeing" the 
JCL error, not sure what GTF trace options to turn on or if it is possible to 
see that JCL error via a GTF trace.

Is it possible to see that JCL error in a GTF trace, if so, what options 
(parms) do I need to run with?



Note: We had an issue with VTAM not coming up on a LPAR and we were unable to 
access JES to see the JCL error.

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN
::DISCLAIMER::

The contents of this e-mail and any attachment(s) are confidential and intended 
for the named recipient(s) only. E-mail transmission is not guaranteed to be 
secure or error-free as information could be intercepted, corrupted, lost, 
destroyed, arrive late or incomplete, or may contain viruses in transmission. 
The e mail and its contents (with or without referred errors) shall therefore 
not attach any liability on the originator or HCL or its affiliates. Views or 
opinions, if any, presented in this email are solely those of the author and 
may not necessarily reflect the views or opinions of HCL or its affiliates. Any 
form of reproduction, dissemination, copying, disclosure, modification, 
distribution and / or publication of this message without the prior written 
consent of authorized representative of HCL is strictly prohibited. If you have 
received this email in error please delete it and notify the sender 
immediately. Before opening any email and/or attachments, please check them for 
viruses and other defects.


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

GTF trace for a JCL error?

[Peter Ten Eyck]

Under z/OS 2.4.

I have a STC when started, fails with the following error in the SYSLOG:

IEE132I START COMMAND DEVICE ALLOCATION ERROR

Looking at the STC output in JES, there is a JCL error in the proc (dataset not 
found).

Is there a way to "see" the JCL error without looking at the JES output?

I have been researching and running a GTF trace with no success "seeing" the 
JCL error, not sure what GTF trace options to turn on or if it is possible to 
see that JCL error via a GTF trace.

Is it possible to see that JCL error in a GTF trace, if so, what options 
(parms) do I need to run with?



Note: We had an issue with VTAM not coming up on a LPAR and we were unable to 
access JES to see the JCL error.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Gtf trace

[Jon Perryman]

On Thu, 11 Jan 2024 16:29:06 +, Ken Bloom  wrote:

>Does anyone know the format of the parm to set the number of bytes recorded to 
>64?

You need to be more specific about what you are tracing. Are you tracing VTAM, 
TCP, RACF or something else? Most likely you will specify size when you tell a 
component to start it's trace.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Gtf trace

[Ken Bloom]

Does anyone know the format of the parm to set the number of bytes recorded to 
64?

Thanks
Ken

Kenneth A. Bloom
CEO
Avenir Technologies Inc
/d/b/a Visara International
203-984-2235
bl...@visara.com
www.visara.com


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Printing GTF trace?

[Jesse 1 Robinson]

Widening the perspective. Versatile IPCS is used to analyze all sorts of 
dumps--SVC, standalone, SYSM--as well as GTF trace, which can be for hardware 
or software or both. So why is it so little used outside of the 'system 
programming' inner sanctum? At my one and only GUIDE conference in 1980, one 
session on IPCS focused on the question of usage. This was in 1980. At that 
time IPCS required SAF READ access to SYS1.PARMLIB. It had to be THE system 
PARMLIB. A copy would not do. The problem for many shops was that access to 
PARMLIB was prohibited by for general users. Meanwhile ISVs rallied to provide 
user-oriented products that cost money--IPCS is 'free'--but did not require 
challenging corporate security policies. 

Somewhere along the line IPCS's PARMLIB requirement was dropped, but it was too 
late to overcome the ISV offerings in the public mind. I was once called in to 
help with a COBOL application that was receiving inexplicable abends. The ISV 
product did not help. I set up a SLIP trap to capture the 'first abend', which 
turned out to be a run of the mill S0C7 caused by bad input data. That abend 
was further mucked up by an ancient SPIE routine that corrupted registers and 
created a different, wholly unrelated abend.

So why is it called 'IPCS' anyway? Interactive Problem Control System. 
Originally IPCS provided an elaborate mechanism for managing an inventory of 
dumps and traces. That function disappeared altogether even as analytical 
functions were enhanced. Like, why is it called 'TSO'? There's no time sharing, 
and it's not optional. Old names persist like those carved on headstones.

.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler 
SHARE MVS Program Co-Manager
323-715-0595 Mobile
626-543-6132 Office ⇐=== NEW
robin...@sce.com

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Colin Paice
Sent: Thursday, April 22, 2021 10:10 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: Printing GTF trace?

*** EXTERNAL EMAIL - Use caution when opening links or attachments ***

For processing IBM product GTF traces you use a command like GTF USR(ALL) to 
process "user" records.

Each product has a format number, MQ has D9.
When a record is processed, the GTF processing in IPCS looks up this format 
number xx, and then invokes a routine AMDUSRxx (or AMDUSRD9  for MQ).
This program takes the record and formats it.
You could write your own formatter.  The basic record structure is well 
documented, but the products specific stuff may not be documented.

These programs typically write to IPCSPRTN, but could write to any other dd 
statement.,

I used to have my own program that did special processing of the data.
This wrote to more than one output dataset.

MVS (Non USR) records have special formatting such as options SSCH, SVC etc.

Colin


On Thu, 22 Apr 2021 at 14:18, Peter Relson  wrote:

> Isn't using file IPCSPRNT the intended way to print something produced 
> by IPCS report(s)?
>
> Allocate data set x with RECFM VBA and suitable LRECL/BLKSIZE such as 
> LRECL 137 BLKSIZE 27998 or LRECL 255 BLKSIZE 6144 TSO ALLOC 
> F(IPCSPRNT) DA(x) do your IPCS commands with the PRINT operand 
> (whether that be GTF or
> other)
> IPCS Close Print
>
> Peter Relson
> z/OS Core Technology Design
--

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Printing GTF trace?

[Colin Paice]

For processing IBM product GTF traces you use a command like
GTF USR(ALL) to process "user" records.

Each product has a format number, MQ has D9.
When a record is processed, the GTF processing in IPCS looks up this format
number xx, and then invokes a routine AMDUSRxx (or AMDUSRD9  for MQ).
This program takes the record and formats it.
You could write your own formatter.  The basic record structure is well
documented, but the products specific stuff may not be documented.

These programs typically write to IPCSPRTN, but could write to any other dd
statement.,

I used to have my own program that did special processing of the data.
This wrote to more than one output dataset.

MVS (Non USR) records have special formatting such as options SSCH, SVC etc.

Colin


On Thu, 22 Apr 2021 at 14:18, Peter Relson  wrote:

> Isn't using file IPCSPRNT the intended way to print something produced by
> IPCS report(s)?
>
> Allocate data set x with RECFM VBA and suitable LRECL/BLKSIZE such as
> LRECL 137 BLKSIZE 27998 or LRECL 255 BLKSIZE 6144
> TSO ALLOC F(IPCSPRNT) DA(x)
> do your IPCS commands with the PRINT operand (whether that be GTF or
> other)
> IPCS Close Print
>
> Peter Relson
> z/OS Core Technology Design
>
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Printing GTF trace?

[Steve Emge]

On Thu, 22 Apr 2021 09:18:03 -0400, Peter Relson  wrote:

>Isn't using file IPCSPRNT the intended way to print something produced by 
>IPCS report(s)?
>
>Allocate data set x with RECFM VBA and suitable LRECL/BLKSIZE such as 
>LRECL 137 BLKSIZE 27998 or LRECL 255 BLKSIZE 6144
>TSO ALLOC F(IPCSPRNT) DA(x) 
>do your IPCS commands with the PRINT operand (whether that be GTF or 
>other) 
>IPCS Close Print  
>
>Peter Relson
>z/OS Core Technology Design
>
. . . 

Yes, that's the method I've always used.  Or, TSO ALLOC FI(IPCSPRNT) 
SYSOUT(class) . . where "class" is a held sysout class.

Then while in IPCS for example,
  GTF CCW PRINT NOTERMINAL
  IPCS CLOSE PRINT

Then, go into SDSF (or IOF) spin the held sysout to a dataset.

In either case, IPCSPRNT to dataset or sysout, then use AMATERSE to terse the 
output then send to vendor.

Regards,
Steve

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Printing GTF trace?

[Peter Relson]

Isn't using file IPCSPRNT the intended way to print something produced by 
IPCS report(s)?

Allocate data set x with RECFM VBA and suitable LRECL/BLKSIZE such as 
LRECL 137 BLKSIZE 27998 or LRECL 255 BLKSIZE 6144
TSO ALLOC F(IPCSPRNT) DA(x) 
do your IPCS commands with the PRINT operand (whether that be GTF or 
other) 
IPCS Close Print  

Peter Relson
z/OS Core Technology Design


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Printing GTF trace?

[Tony Thigpen]

Thanks. I will try it tomorrow.

Tony Thigpen

(K.K.Paradox)T.Kobayashi wrote on 4/21/21 10:16 PM:

Hello Tony,

Here is GTF trace print JCL:

a) You need to modify it for your environment (DSN, VOLUME, etc...).
b) INPUT DD of the IKJEFT01 step specifies the GTF trace file.
   This sample trace file is tape file.
c) The report is output to the JES spool,if you need to report to disk.
   Change the SYSTSPRT DD card to VBA datasets.
d) Specify your required trace with the GTF xxx command on SYSTSIN DD card.
   This sample is CCW trace.

//GTFPRINT  JOB CLASS=A
//ST1  EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//SYSIN    DD *
DEFINE CLUSTER(NAME(KOBA.IPCS.DIR) VOLUME(WORK01)) -
   DATA(NAME(KOBA.IPCS.DIR.DATA) CYL(1 1) KEYS(128 0) -
    CISZ(X'1000') ) -
  INDEX(NAME(KOBA.IPCS.DIR.INDEX) TRK(1 1) )
/*
//IPCS    EXEC PGM=IKJEFT01,DYNAMNBR=20
//IPCSDDIR DD  DSN=KOBA.IPCS.DIR,DISP=SHR
//***IPCSPARM DD  DSN=
//INPUT    DD  DSN=SYS1.TRACE,DISP=SHR,VOL=SER=GTRACE,UNIT=/4000,
// LABEL=(1,SL,EXPDT=98000)
//SYSPROC  DD  DSN=SYS1.SBLSCLI0,DISP=SHR
//SYSTSPRT DD  SYSOUT=*
//SYSTSIN  DD  *
IPCSDDIR 'KOBA.IPCS.DIR'
IPCS NOPARM
SETDEF DDNAME(INPUT) NOCONFIRM
SETDEF LIST
GTF CCW
END
/*
//STLAST   EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//SYSIN    DD *
DELETE (KOBA.IPCS.DIR)
/*

I hope this help.

Best regards,
Toyokazu Kobayashi

- Original Message - From: "Tony Thigpen" 
Newsgroups: bit.listserv.ibm-main
To: 
Sent: Thursday, April 22, 2021 4:15 AM
Subject: Printing GTF trace?



All,

I have generated a GTF trace for a vendor, but how do I generate a 
print report of the formatted entries so I can send them to a vendor?


I can browse the formatted entries in IPCS, but I am new to IPCS and 
don't know how to tell it to print the entire report.


Tony Thigpen

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN



--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Printing GTF trace?

[(K.K.Paradox)T.Kobayashi]

Hello Tony,

Here is GTF trace print JCL:

a) You need to modify it for your environment (DSN, VOLUME, etc...).
b) INPUT DD of the IKJEFT01 step specifies the GTF trace file.
  This sample trace file is tape file.
c) The report is output to the JES spool,if you need to report to disk.
  Change the SYSTSPRT DD card to VBA datasets.
d) Specify your required trace with the GTF xxx command on SYSTSIN DD card.
  This sample is CCW trace.

//GTFPRINT  JOB CLASS=A
//ST1  EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//SYSINDD *
DEFINE CLUSTER(NAME(KOBA.IPCS.DIR) VOLUME(WORK01)) -
  DATA(NAME(KOBA.IPCS.DIR.DATA) CYL(1 1) KEYS(128 0) -
   CISZ(X'1000') ) -
 INDEX(NAME(KOBA.IPCS.DIR.INDEX) TRK(1 1) )
/*
//IPCSEXEC PGM=IKJEFT01,DYNAMNBR=20
//IPCSDDIR DD  DSN=KOBA.IPCS.DIR,DISP=SHR
//***IPCSPARM DD  DSN=
//INPUTDD  DSN=SYS1.TRACE,DISP=SHR,VOL=SER=GTRACE,UNIT=/4000,
// LABEL=(1,SL,EXPDT=98000)
//SYSPROC  DD  DSN=SYS1.SBLSCLI0,DISP=SHR
//SYSTSPRT DD  SYSOUT=*
//SYSTSIN  DD  *
IPCSDDIR 'KOBA.IPCS.DIR'
IPCS NOPARM
SETDEF DDNAME(INPUT) NOCONFIRM
SETDEF LIST
GTF CCW
END
/*
//STLAST   EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//SYSINDD *
DELETE (KOBA.IPCS.DIR)
/*

I hope this help.

Best regards,
Toyokazu Kobayashi

- Original Message - 
From: "Tony Thigpen" 

Newsgroups: bit.listserv.ibm-main
To: 
Sent: Thursday, April 22, 2021 4:15 AM
Subject: Printing GTF trace?



All,

I have generated a GTF trace for a vendor, but how do I generate a print 
report of the formatted entries so I can send them to a vendor?


I can browse the formatted entries in IPCS, but I am new to IPCS and 
don't know how to tell it to print the entire report.


Tony Thigpen

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN



--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Printing GTF trace?

[Tony Thigpen]

Yes. Print to file.
But, I just sent them the trace file that I downloaded from z/OS.

Tony Thigpen

Gord Tomlin wrote on 4/21/21 4:44 PM:

On 2021-04-21 15:15 PM, Tony Thigpen wrote:

All,

I have generated a GTF trace for a vendor, but how do I generate a 
print report of the formatted entries so I can send them to a vendor?


I can browse the formatted entries in IPCS, but I am new to IPCS and 
don't know how to tell it to print the entire report.


Did they specifically ask for it in printed form? We normally ask 
customers to terse the GTF trace and send us the tersed file. Then, we 
can use IPCS on it.


--

Regards, Gord Tomlin
Action Software International
(a division of Mazda Computer Corporation)
Tel: (905) 470-7113, Fax: (905) 470-6507
Support: https://actionsoftware.com/support/

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Printing GTF trace?

[Gord Tomlin]

On 2021-04-21 15:15 PM, Tony Thigpen wrote:

All,

I have generated a GTF trace for a vendor, but how do I generate a 
print report of the formatted entries so I can send them to a vendor?


I can browse the formatted entries in IPCS, but I am new to IPCS and 
don't know how to tell it to print the entire report.



Did they specifically ask for it in printed form? We normally ask customers to 
terse the GTF trace and send us the tersed file. Then, we can use IPCS on it.

--

Regards, Gord Tomlin
Action Software International
(a division of Mazda Computer Corporation)
Tel: (905) 470-7113, Fax: (905) 470-6507
Support: https://actionsoftware.com/support/

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Printing GTF trace?

[Carmen Vitullo]

I've only performed this once for a vendor in batch and tersed the print to 
them 
  
IPCS GTF CCW(option) PRINT 
   
Carmen Vitullo 

   

-Original Message-

From: Tony 
To: IBM-MAIN 
Date: Wednesday, 21 April 2021 2:16 PM CDT
Subject: Printing GTF trace?

All, 

I have generated a GTF trace for a vendor, but how do I generate a print 
report of the formatted entries so I can send them to a vendor? 

I can browse the formatted entries in IPCS, but I am new to IPCS and 
don't know how to tell it to print the entire report. 

Tony Thigpen 

-- 
For IBM-MAIN subscribe / signoff / archive access instructions, 
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN   

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Printing GTF trace?

[Tony Thigpen]

All,

I have generated a GTF trace for a vendor, but how do I generate a print 
report of the formatted entries so I can send them to a vendor?


I can browse the formatted entries in IPCS, but I am new to IPCS and 
don't know how to tell it to print the entire report.


Tony Thigpen

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Problem reading GTF trace output

[Greg Dyck]

On 3/16/2017 2:30 AM, kalda0...@gmail.com wrote:
> When I try to format the trace in IPCS the following error is received:
>
> BLS21082I DSNAME('SYS1.TRACE')I/O error
> BLS21081I 0AB1,D,SYS00010,READ,OUT OF EXTENT,TTR UNKNOWN,BSAM
> AHL10004I Input is not a GTF trace dataset.
> AHL10009I No records of the requested type were found.

Based on the IPCS messages, I believe your dump direct already contains 
records for a prior SYS1.TRACE dataset incarnation.  Issue the command-


  IP DROPD DA('SYS1.TRACE')

to delete those records, and then you should be able to format the new data.

Regards,
Greg

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN