Re: length of "executable"

>PDS2STOR Or PMAR_STOR (IEWPMAR coupled with IGWSMDE) from DESERV GET. Peter Relson z/OS Core Technology Design -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the

Re: length of "executable" (I meant Re: Inquire intrdr default job class)

Ouch! I hybridized two threads. I meant to reply to "inquire intrdr" but posted instead to "length of executable". On Tue, 8 Dec 2015 00:44:57 -0600, Elardus Engelbrecht wrote: >Shmuel Metz (Seymour J.) wrote: > >>>The first restriction I see is: >>

Re: length of "executable"

Any reason to prefer one over the other? Frank > Date: Tue, 8 Dec 2015 07:34:40 -0500 > From: rel...@us.ibm.com > Subject: Re: length of "executable" > To: IBM-MAIN@LISTSERV.UA.EDU > > >PDS2STOR > > Or PMAR_STOR (IEWPMAR coupled with IGWSMDE) from DESE

Re: length of "executable"

Shmuel Metz (Seymour J.) wrote: >>The first restriction I see is: >>The CONSOLE host command environment is available only to REXX execs that >> run in the TSO/E address space. >And SDSF is available without TSO? Yes, look at EXEC PGM=ISFAFD. [1] Groete / Greetings Elardus Engelbrecht

Re: length of "executable"

On Mon, 7 Dec 2015 11:15:29 -0600, Paul Gilmartin (whoever) wrote: > >I'll read doc for SDSF to see whether its API provides a way to capture output >from operator commands it issues. > So: in:

Re: length of "executable"

the exact length value (not rounded up to the next 4K or whatever) I a bit perplexed as to why this (whatever their methods are) appears to be something not readily available to me. Frank > Date: Sat, 5 Dec 2015 18:43:20 -0500 > From: shmuel+ibm-m...@patriot.net > Subject: Re: length of &q

Re: length of "executable"

> Peter mentioned trying BLDL or DESERV. I don't see that BLDL > provides a length result. Am I missing something? I can't see > where DESERV provides this information either. > > Since there appears to be a way that ISPF and CICS can get the exact > length value (not rounded up to the next

Re: length of "executable"

In , on 12/07/2015 at 09:44 AM, Frank Swarbrick said: >Peter mentioned trying BLDL or DESERV. I don't see that BLDL >provides a length result. It's in the user data. >Am I missing something? Yes, IHAPDS. --

Re: length of "executable"

On Mon, 7 Dec 2015 09:44:06 -0700, Frank Swarbrick wrote: > This! >:-) > >I didn't know how to explain it, sorry. > >Peter mentioned trying BLDL or DESERV. I don't see that BLDL provides a >length result. Am I missing something? I can't see where DESERV provides >this information either. >

Re: length of "executable"

On Mon, 7 Dec 2015 12:57:23 -0500, Shmuel Metz (Seymour J.) wrote: > >Why use SDSF at all unless you need other SDSF facilities? If you're >writing in REXX, the CONSOLE interface is the obvious way to retrieve >command responses. > The first restriction I see is: The CONSOLE host command

Re: length of "executable"

Looks like field PDS2STOR (TOTAL CONTIGUOUS VIRTUAL STORAGE REQUIREMENT OF MODULE) is the number I am looking for. Thanks to all who helped! Frank > Date: Mon, 7 Dec 2015 12:50:18 -0500 > From: shmuel+ibm-m...@patriot.net > Subject: Re: length of "executable" > To: IB

Re: length of "executable"

In <9856217046987844.wa.paulgboulderaim@listserv.ua.edu>, on 12/07/2015 at 11:30 AM, Paul Gilmartin <000433f07816-dmarc-requ...@listserv.ua.edu> said: >REXX: Use ISFSLASH. See Issuing system commands with ISFSLASH. Why use SDSF at all unless you need other SDSF facilities? If

Re: length of "executable"

In <4504029974950910.wa.paulgboulderaim@listserv.ua.edu>, on 12/07/2015 at 01:42 PM, Paul Gilmartin <000433f07816-dmarc-requ...@listserv.ua.edu> said: >On Mon, 7 Dec 2015 12:57:23 -0500, Shmuel Metz (Seymour J.) wrote: > >>Why use SDSF at all unless you need other SDSF facilities? If

Re: length of "executable"

>1. Why are you using EXTINFO? Using EXTINFO can avoid having also to use CSVQUERY for an RMODE=SPLIT module. The book section quoted could/should be updated to mention that possibility, since that is why I implemented it. >>You did not explain why you might "need" 36B0 hex. >He's loading a

Re: length of "executable"

>36B0 hex = 14000 decimal, and that is the length I am expecting. Your expectation is not correct. The length returned (both in R1 as the number of doublewords, or via EXTINFO) represents the amount of space that the system obtains. Particularly for program objects, it is often the case that

Re: length of "executable"

On Sat, 5 Dec 2015 09:49:45 -0500, Peter Relson wrote: >>36B0 hex = 14000 decimal, and that is the length I am expecting. > >You did not explain why you might "need" 36B0 hex. > It might be the size of a table, not otherwise known at execution time. I'd suggest a header to the table containing

Re: length of "executable"

In , on 12/04/2015 at 05:54 PM, Frank Swarbrick said: >I am able to use the LOAD macro to get the address, but I also need >to get the length. >From z/OS MVS Programming: Assembler Services Reference, Volume 2

Re: length of "executable"

In , on 12/04/2015 at 07:18 PM, Mike Schwab said: >A PDS load module block is a multiple of 1K. No. >PDSEs are built on linear datasets I doubt that that's relevant. -- Shmuel (Seymour J.)

Re: length of "executable"

In <201512051447.tb5eldfi004...@d01av05.pok.ibm.com>, on 12/05/2015 at 09:49 AM, Peter Relson said: >You did not explain why you might "need" 36B0 hex. He's loading a table and needs both the address and length in order to process it. -- Shmuel (Seymour J.) Metz,

Re: length of "executable"

In , on 12/04/2015 at 08:10 PM, John McKown said: > I don't know what EXTINFO refers to off-hand, but supposedly R1 >upon return contains the length, in double word increments, of the >module

Re: length of "executable"

A PDS load module block is a multiple of 1K. PDSEs are built on linear datasets (VSAM) so it might be a 4K multiple. On Fri, Dec 4, 2015 at 6:54 PM, Frank Swarbrick wrote: > Currently we have some assembler 'data only programs' that we load under CICS > and point

length of "executable"

Currently we have some assembler 'data only programs' that we load under CICS and point to, i.e.: EXEC CICS LOAD PROGRAM ('XML1V2K') SET (ADDRESS OF CRD-SOURCE-AREA) FLENGTH (CRD-SOURCE-LEN) END-EXEC

Re: length of "executable"

On Fri, Dec 4, 2015 at 6:54 PM, Frank Swarbrick wrote: > Currently we have some assembler 'data only programs' that we load under > CICS and point to, i.e.: > > EXEC CICS LOAD > PROGRAM ('XML1V2K') > SET (ADDRESS OF CRD-SOURCE-AREA) > FLENGTH