Re: STOW macro Location

2011-11-15 Thread Elardus Engelbrecht
To Binyamin Dissen and Shmuel Metz: Ok, I must be confusing (having too much decaying braincells :D ) STOW with something else which can destroy a PDS / PDSE directory if used incorrectly. Please educate and correct me what that thing was which was discussed on IBM-MAIN. I remember that if you

Re: STOW macro Location

2011-11-15 Thread Paul Gilmartin
On Tue, 15 Nov 2011 04:56:39 -0600, Elardus Engelbrecht wrote: Ok, I must be confusing (having too much decaying braincells :D ) STOW with something else which can destroy a PDS / PDSE directory if used incorrectly. It used to be easy enough with IEBGENER. This may have changed lately, or may

Re: STOW macro Location

2011-11-15 Thread Shmuel Metz (Seymour J.)
In 1009418597484101.wa.elardus.engelbrechtsita.co...@bama.ua.edu, on 11/15/2011 at 04:56 AM, Elardus Engelbrecht elardus.engelbre...@sita.co.za said: Ok, I must be confusing (having too much decaying braincells :D ) STOW with something else which can destroy a PDS / PDSE directory if used

Re: STOW macro Location

2011-11-15 Thread Shmuel Metz (Seymour J.)
In 7i53c7thv9cglid3773mjl4k778pvp3...@4ax.com, on 11/15/2011 at 12:30 AM, Binyamin Dissen bdis...@dissensoftware.com said: Incorrect. Closer than your answer. The mapping macro has a parameter to indicate whether the BLDL or directory format is desired. Not for PDSE. -- Shmuel

Re: STOW macro Location

2011-11-15 Thread Paul Gilmartin
On Tue, 15 Nov 2011 09:08:25 -0500, Shmuel Metz (Seymour J.) wrote: In 1009418597484101.wa.elardus.engelbrechtsita.co...@bama.ua.edu, on 11/15/2011 at 04:56 AM, Elardus Engelbrecht said: Ok, I must be confusing (having too much decaying braincells :D ) STOW with something else which can destroy

Re: STOW macro Location

2011-11-15 Thread Gerhard Postpischil
On 11/15/2011 5:56 AM, Elardus Engelbrecht wrote: To Binyamin Dissen and Shmuel Metz: Ok, I must be confusing (having too much decaying braincells :D ) STOW with something else which can destroy a PDS / PDSE directory if used incorrectly. Or perhaps you were thinking of STOW ,,,I ? Re your

Re: STOW macro Location

2011-11-15 Thread Rick Fochtman
---snip Ok, I must be confusing (having too much decaying braincells :D ) STOW with something else which can destroy a PDS / PDSE directory if used incorrectly. Please educate and correct me what that thing was which was

Re: STOW macro Location

2011-11-15 Thread Bill Fairchild
Sent: Tuesday, November 15, 2011 2:22 PM To: IBM-MAIN@bama.ua.edu Subject: Re: STOW macro Location ---snip Ok, I must be confusing (having too much decaying braincells :D ) STOW with something else which can destroy a PDS / PDSE

Re: STOW macro Location

2011-11-15 Thread Jim Thomas
(res) j...@thethomasresidence.us (Email) -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Bill Fairchild Sent: Tuesday, November 15, 2011 6:39 PM To: IBM-MAIN@bama.ua.edu Subject: Re: STOW macro Location STOW does not ever

Re: STOW macro Location

2011-11-15 Thread Shane
On Wed, 16 Nov 2011 00:38:34 + Bill Fairchild wrote: Perhaps IBM reasoned that if a user really, really, seriously wants to do something this strange, they should let him. Your gun, your foot ... Maybe users in bygone times were made of sterner stuff and prepared to take responsibility for

Re: STOW macro Location

2011-11-15 Thread Gerhard Postpischil
On 11/15/2011 7:38 PM, Bill Fairchild wrote: I think the real culprit is the lack of user-friendliness in whatever OPEN executor module is blindly following the user's request to overwrite an entire file without checking for certain file types for which overwriting the whole file might not be

Re: STOW macro Location

2011-11-15 Thread John Gilmore
Shane's point is an important one. In a private email to Bill earlier this evening I confessed that I had (more than once) opened a PDS as a sequential data set using BSAM in order to read a (mangled) directory. On the occasion I remember best I got the information I needed without [further]

Re: STOW macro Location

2011-11-15 Thread Gerhard Postpischil
On 11/15/2011 8:41 PM, Shane wrote: Maybe users in bygone times were made of sterner stuff and prepared to take responsibility for their own actions. Not necessarily - we operated in a completely different environment. There were so few manuals that it was possible to read all of them, as

Re: STOW macro Location

2011-11-15 Thread Paul Gilmartin
On Tue, 15 Nov 2011 20:51:25 -0500, Gerhard Postpischil wrote: On 11/15/2011 7:38 PM, Bill Fairchild wrote: I think the real culprit is the lack of user-friendliness in whatever OPEN executor module is blindly following the user's request to overwrite an entire file without checking for

Re: STOW macro Location

2011-11-15 Thread Shmuel Metz (Seymour J.)
In 1149164858762620.wa.paulgboulderaim@bama.ua.edu, on 11/15/2011 at 09:39 AM, Paul Gilmartin paulgboul...@aim.com said: Indirectly. Right answer to wrong question. Rexx (even in batch, under IKJEFT*) can invoke ISPF to use ISPF services. You're still talking about ISPF services, not

Re: STOW macro Location

2011-11-15 Thread Shmuel Metz (Seymour J.)
In 2016114137.2cca11dd@xpfs, on 11/16/2011 at 11:41 AM, Shane ibm-m...@tpg.com.au said: Maybe IBM never put any thought into it at all. That would certain account for absolute track 0 not available when you forgot a SPACE keyword for a new data set. -- Shmuel (Seymour J.) Metz,

Re: STOW macro Location

2011-11-15 Thread Shmuel Metz (Seymour J.)
In CAPD5F5qvUFtSVX3WoWvHNmTfPObydZuusnbx+MV0mAWS=fq...@mail.gmail.com, on 11/15/2011 at 09:01 PM, John Gilmore johnwgilmore0...@gmail.com said: Would I discourage a novice from doing this sort of thing? Yes, but Do what I say, not what I do is not always unreasonable, although it is of course

Re: STOW macro Location

2011-11-15 Thread Gerhard Postpischil
On 11/15/2011 9:24 PM, Paul Gilmartin wrote: Resource constraint, whether development schedule or REGION to accommodate the executable code is a plausible explanation. All of the OPEN code was in a type 4 SVC, with a 1K constraint on each transient. While OPEN had a lot of overlays, it didn't

STOW macro Location

2011-11-14 Thread jagadishan perumal
Hi, Could anyone please point me to the STOW macro Library location in Z/os. Where I can see the Assembler codes Responsible for PDS/PDSE directory update by STOW. I referred this Link : http://publib.boulder.ibm.com/infocenter/zvm/v5r4/index.jsp?topic=/com.ibm.zos.r9.ieab200/destow.htm but Not

Re: STOW macro Location

2011-11-14 Thread Lizette Koehler
Hi, Could anyone please point me to the STOW macro Library location in Z/os. Where I can see the Assembler codes Responsible for PDS/PDSE directory update by STOW. I referred this Link : http://publib.boulder.ibm.com/infocenter/zvm/v5r4/index.jsp?topic=/com .ibm.zos.r9.ie

Re: STOW macro Location

2011-11-14 Thread Lizette Koehler
Hi, Could anyone please point me to the STOW macro Library location in Z/os. Where I can see the Assembler codes Responsible for PDS/PDSE directory update by STOW. I referred this Link : http://publib.boulder.ibm.com/infocenter/zvm/v5r4/index.jsp?topic=/com.ibm.z os.r9.ie

Re: STOW macro Location

2011-11-14 Thread Binyamin Dissen
On Mon, 14 Nov 2011 15:31:46 +0530 jagadishan perumal jagadish...@gmail.com wrote: :Could anyone please point me to the STOW macro Library location in Z/os. SYS1.MACLIB :Where I can see the Assembler codes Responsible for PDS/PDSE directory :update by STOW. :I referred this Link :

Re: STOW macro Location

2011-11-14 Thread J R
; second 8 bytes contain the new member name or alias. Date: Mon, 14 Nov 2011 15:31:46 +0530 From: jagadish...@gmail.com Subject: STOW macro Location To: IBM-MAIN@bama.ua.edu Hi, Could anyone please point me to the STOW macro Library location in Z/os. Where I can see the Assembler codes

Re: STOW macro Location

2011-11-14 Thread John McKown
Most of the macros that are z/OS BCP (Base Control Program) related reside either in SYS1.MACLIB or SYS1.MODGEN. STOW is in SYS1.MACLIB. On Mon, 2011-11-14 at 15:31 +0530, jagadishan perumal wrote: Hi, Could anyone please point me to the STOW macro Library location in Z/os. Where I can see

Re: STOW macro Location

2011-11-14 Thread Elardus Engelbrecht
jagadishan perumal wrote: Could anyone please point me to the STOW macro Library location in Z/os. Where I can see the Assembler codes Responsible for PDS/PDSE directory update by STOW. Why? What are you trying to achieve? One little error and you whole PDS/PDSE is destroyed and it is goodbye

Re: STOW macro Location

2011-11-14 Thread Binyamin Dissen
On Mon, 14 Nov 2011 07:26:14 -0600 Elardus Engelbrecht elardus.engelbre...@sita.co.za wrote: :jagadishan perumal wrote: :Could anyone please point me to the STOW macro Library location in Z/os. Where I can see the Assembler codes Responsible for PDS/PDSE directory update by STOW. :Why? What

Re: STOW macro location

2011-11-14 Thread John Gilmore
reposted from the assembler list, where I put it first in error: I suspect that what Jagadishan wants to know is where, physically, in what crypto-DASD PDS[E], the STOW macro definition is to be found. Is it, say in SYS!.MACLIB? Elsewhere with other data-management macros? Such questions are

Re: STOW macro Location

2011-11-14 Thread Shmuel Metz (Seymour J.)
In canhhcytp0vz+uzu3r-ibjqejw4t8v-kyoahkuyzdk_u0rjm...@mail.gmail.com, on 11/14/2011 at 03:31 PM, jagadishan perumal jagadish...@gmail.com said: Could anyone please point me to the STOW macro Library location in Z/os. SYS1.MACLIB. Where I can see the Assembler codes Responsible for PDS/PDSE

Re: STOW macro Location

2011-11-14 Thread Shmuel Metz (Seymour J.)
In 012b01cca2bd$61013710$2303a530$@mindspring.com, on 11/14/2011 at 06:05 AM, Lizette Koehler stars...@mindspring.com said: I was not aware that the STOW would also work on a PDSE. How could it not? There would be no upward compatibility without it. PDSE directory entry returned by DESERV

Re: STOW macro Location

2011-11-14 Thread Shmuel Metz (Seymour J.)
In 5909987196980741.wa.elardus.engelbrechtsita.co...@bama.ua.edu, on 11/14/2011 at 07:26 AM, Elardus Engelbrecht elardus.engelbre...@sita.co.za said: Why? What are you trying to achieve? One little error and you whole PDS/PDSE is destroyed and it is goodbye to your nice PDS/PDSE ... What

Re: STOW macro Location

2011-11-14 Thread Bill Fairchild
Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Shmuel Metz (Seymour J.) Sent: Monday, November 14, 2011 11:51 AM To: IBM-MAIN@bama.ua.edu Subject: Re: STOW macro Location In canhhcytp0vz+uzu3r-ibjqejw4t8v-kyoahkuyzdk_u0rjm...@mail.gmail.com, on 11/14/2011 at 03:31 PM, jagadishan perumal

Re: STOW macro Location

2011-11-14 Thread tony's netbook
On 11/14/2011 7:26 AM, Elardus Engelbrecht wrote: jagadishan perumal wrote: Could anyone please point me to the STOW macro Library location in Z/os. Where I can see the Assembler codes Responsible for PDS/PDSE directory update by STOW. Why? What are you trying to achieve? One little error

Re: STOW macro Location

2011-11-14 Thread Shmuel Metz (Seymour J.)
In 77142d37c0c3c34da0d7b1da7d7ca3433225e...@nwt-s-mbx2.rocketsoftware.com, on 11/14/2011 at 06:06 PM, Bill Fairchild bfairch...@rocketsoftware.com said: The results of a STOW macro's having executed can be seen in the mapping macro IHAPDS, which maps the directory entry for a PDS or a PDSE.

Re: STOW macro Location

2011-11-14 Thread Binyamin Dissen
On Mon, 14 Nov 2011 14:58:29 -0500 Shmuel Metz (Seymour J.) shmuel+ibm-m...@patriot.net wrote: :In :77142d37c0c3c34da0d7b1da7d7ca3433225e...@nwt-s-mbx2.rocketsoftware.com, :on 11/14/2011 : at 06:06 PM, Bill Fairchild bfairch...@rocketsoftware.com said: :The results of a STOW macro's having