Article View: bit.listserv.asm370
Article #250Re: How to find PDS member name details
From: Tuben, Gregg
Date: Wed, 26 Oct 2005 18:10
Date: Wed, 26 Oct 2005 18:10
38 lines
3503 bytes
3503 bytes
Mike, If you are not set on solving the original problem as originally stated and just want to set the IMS parms properly, couldn't you change the parm in a JES exit? It has been 20 years but I remember doing something like this to solve a problem with hard coded volume names. Gregg Tuben BMC Software Inc. -----Original Message----- From: IBM Mainframe Assembler List [mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU] On Behalf Of Mike Baker Sent: Tuesday, October 25, 2005 1:25 AM To: ASSEMBLER-LIST@LISTSERV.UGA.EDU Subject: Re: How to find PDS member name details The problem is an extremely messy environment. Years ago some standard IMS database procedures were created, and people were meant to execute the centrally stored procs, and use whatever JCL overrides they needed. Now... 18 years later, everyone their own personal version/s of the procs, and they execute these most (not all) of the time. The test environment is a complete mess, and no-one has a clue what's going on. IMS version 7.1 does not force the use of the DBRC=Y parameter in the JCL, and whilst you can code it in the centrally stored procs, that is no help if people don't use those procs. Nor do they want anyone telling them what they should be using... even though their own source libraries are now in a state of complete chaos. So... the intention would be to write a front-end for the IMS region controller program, rename the IBM one, and XCTL to it after extracting various items of info. such as the PDS member name details. And with the gathering of this information, then control can be established.
Technical Details
Message-ID:
<E9DE7963E5EA6546B42A979EC28B4D0106AFC60C@hou-ex-02.adprod.bmc.com>Path:
arc1-ca.pugleaf.net!g2news1.google.com!news3.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!newscon06.news.prodigy.com!prodigy.net!news-feed01.roc.ny.frontiernet.net!nntp.frontiernet.net!newsfeed2.easynews.com!newsfeed1.easynews.com!easynews.com!easynews!sn-xit-02!sn-xit-12!sn-xit-09!sn-xit-14!supernews.com!149.173.6.116.MISMATCH!foggy!vm.sas.com!bmc.com!Gregg_TubenShow 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!news3.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!newscon06.news.prodigy.com!prodigy.net!news-feed01.roc.ny.frontiernet.net!nntp.frontiernet.net!newsfeed2.easynews.com!newsfeed1.easynews.com!easynews.com!easynews!sn-xit-02!sn-xit-12!sn-xit-09!sn-xit-14!supernews.com!149.173.6.116.MISMATCH!foggy!vm.sas.com!bmc.com!Gregg_Tuben
From: "Tuben, Gregg" <Gregg_Tuben@bmc.com>
Newsgroups: bit.listserv.asm370
Subject: Re: How to find PDS member name details
Date: Wed, 26 Oct 2005 13:10:31 -0500
Organization: SAS Inc.
Lines: 38
Sender: IBM Mainframe Assembler List <ASSEMBLER-LIST@LISTSERV.UGA.EDU>
Message-ID: <E9DE7963E5EA6546B42A979EC28B4D0106AFC60C@hou-ex-02.adprod.bmc.com>
NNTP-Posting-Host: mozart.unx.sas.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Trace: foggy.unx.sas.com 1130350834 10753 10.19.150.41 (26 Oct 2005 18:20:34 GMT)
X-Complaints-To: usenet@unx.sas.com
NNTP-Posting-Date: Wed, 26 Oct 2005 18:20:34 +0000 (UTC)
Comments: Gated by NETNEWS@VM.SAS.COM
Return-Path: <owner-assembler-list@LISTSERV.UGA.EDU>
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
Thread-Topic: Re: How to find PDS member name details
Thread-Index: AcXZLSHcubf9ccvTSzC/t5LiXGJASgBKTXJg
X-OriginalArrivalTime: 26 Oct 2005 18:10:31.0980 (UTC)
FILETIME=[8DBBCEC0:01C5DA58]
X-MIME-Autoconverted: from quoted-printable to 8bit by listserv.cc.uga.edu id
j9QIAWqB022095
Approved-By: "Tuben, Gregg" <Gregg_Tuben@BMC.COM>
Return-Path: owner-assembler-list@LISTSERV.UGA.EDU
X-Mime-Autoconverted: from 8bit to 7bit by mime827
Originator: daemon@mozart.unx.sas.com