Article View: bit.listserv.asm370
Article #214Re: How to find PDS member name details
From: Robert A. Rosenberg
Date: Tue, 25 Oct 2005 03:29
Date: Tue, 25 Oct 2005 03:29
27 lines
3211 bytes
3211 bytes
At 17:09 -0700 on 10/24/2005, Edward E. Jaffe wrote about Re: How to find PDS member name details: >Mike Baker wrote: > > >2: The full-name of the JCL member which was used to execute the Procedure? >> >>eg: If inside dataset "MY.PDS.JCL" there is a member called "PROGRUN", and >>this executes a PDS member called "MY.PDS.PROCLIB(PROCRUN)", and inside the >>Procedure "PROCRUN" it executes a program called "PROG001", then I would >>like "PROG001" to either issue some Macro/s or chain through MVS Control >>Blocks in order to find the answers to questions 1 + 2 above. >> >> > >If I understand what you've written above, you won't be able to get this. The information IS available - The question is if it is accessible while the step is running. If you look at the JCL Listing of a job that invokes a proc (that is loaded from a Proclib) you will note a message that lists the Member Name of the Proc as well as the DSN of the Proclib that it was fetched from. The question is how to access this JCL listing (and if it can be accessed). Given that SDSF can list this while the job is running, I'd say that, at least theoretically, you should be able to run Control Block chains and/or issue commands to gain access to this data (ie: Use the same type of interface code that SDSF does).
Technical Details
Message-ID:
<p06230906bf8355541078@[192.168.1.11]>Path:
arc1-ca.pugleaf.net!g2news1.google.com!news4.google.com!news.glorb.com!newsfeed2.easynews.com!newsfeed1.easynews.com!easynews.com!easynews!sn-xit-02!sn-xit-06!sn-xit-14!supernews.com!149.173.6.116.MISMATCH!foggy!vm.sas.com!rarpsl.com!asmReferences:
<200510242133.j9OKaWeA031464@malibu.cc.uga.edu> <435D77A8.5010205@phoenixsoftware.com>Show Full Headers
Complete Article Headers
X-Google-Thread: fcdcb,21dc5dfdb7ef5f7f
X-Google-Attributes: gidfcdcb,public
X-Google-Language: ENGLISH,ASCII-7-bit
Path: arc1-ca.pugleaf.net!g2news1.google.com!news4.google.com!news.glorb.com!newsfeed2.easynews.com!newsfeed1.easynews.com!easynews.com!easynews!sn-xit-02!sn-xit-06!sn-xit-14!supernews.com!149.173.6.116.MISMATCH!foggy!vm.sas.com!rarpsl.com!asm
From: "Robert A. Rosenberg" <asm@rarpsl.com>
Newsgroups: bit.listserv.asm370
Subject: Re: How to find PDS member name details
Date: Mon, 24 Oct 2005 23:29:48 -0400
Organization: SAS Inc.
Lines: 27
Sender: IBM Mainframe Assembler List <ASSEMBLER-LIST@LISTSERV.UGA.EDU>
Message-ID: <p06230906bf8355541078@[192.168.1.11]>
References: <200510242133.j9OKaWeA031464@malibu.cc.uga.edu>
<435D77A8.5010205@phoenixsoftware.com>
NNTP-Posting-Host: mozart.unx.sas.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Trace: foggy.unx.sas.com 1130211289 7115 10.19.150.41 (25 Oct 2005 03:34:49 GMT)
X-Complaints-To: usenet@unx.sas.com
NNTP-Posting-Date: Tue, 25 Oct 2005 03:34:49 +0000 (UTC)
Comments: Gated by NETNEWS@VM.SAS.COM
Return-Path: <owner-assembler-list@LISTSERV.UGA.EDU>
X-Mailer: Eudora for Mac OS X 6.2.3 (MacOS 10.3)
X-AntiAbuse: This header was added to track abuse,
please include it with any abuse report
X-AntiAbuse: Primary Hostname - server70.totalchoicehosting.com
X-AntiAbuse: Original Domain - listserv.uga.edu
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - rarpsl.com
Approved-By: "Robert A. Rosenberg" <asm@RARPSL.COM>
In-Reply-To: <435D77A8.5010205@phoenixsoftware.com>
Return-Path: owner-assembler-list@LISTSERV.UGA.EDU
X-OriginalArrivalTime: 25 Oct 2005 03:34:46.0752 (UTC)
FILETIME=[0BEC8E00:01C5D915]
Originator: daemon@mozart.unx.sas.com