Maybe you can use the length in the text file, depending on Steve's
intended use. If the text file does not have external references
which are resolved at load time, then maybe he can use the length
in the ESD record+29 for a length of 3:
MVCIN TEXT A1 F 80 Trunc=72 Size=6 Line=0 Col=1 Alt=0
====>
|...+....1....+....2....+....3....+....4....+....5....+....6....+....7.>.
* * * Top of File * * *
00000
|...+....1....+....2....+....3....+....4....+....5....+....6....+....7...
"ESD "" ""MVCIN """""""{ 0
00001
0CEC444444014400DECCD4440000000C
25240000000000014539500000000000
"TXT """ "" ""°Ö}""õ&}0À °0-&°}"""á"{"TYPLIN """©B""""""""Y"{y{×á"{ç0
00002
"TXT """ "" ""TYPLIN """yB"""""""+ì}{ÀqÖ}""""Ú 0
00003
"TXT ""y "" "" !DLROW OLLEH 0
00004
"RLD "" """"""""""""""" """¢ 0
00005
"END """ "" 1569623400 010198350 0
00006
* * * End of File * * *
00007
This value is 0000C0. Looking at the assembly listing for this text
file, we see:
MVCIN LISTING A1 F 133 Trunc=72 Size=187 Line=37 Col=1 Alt=0
====>
PF key definition file DEFAULT now active.
" XREF(FULL)
00037
"
00038
" NO OVERRIDING DD NAMES
00039
»
00040
" EXTERNAL SYMBOL DICTIONARY
00041
"SYMBOL TYPE ID ADDR LENGTH LD ID FLAGS ALIAS-OF
00042
"MVCIN SD 0001 000000 0000C0 00
00043
»
00044
"
00045
This may be good enough for what Steve needs, if his text file doesn't
contain external references that
get resolved at load time.
Regards,
Bill Stephens
Sr. Technology Analyst, High Availability
SunGard Availability Services
10th floor
401 North Broad Street
Philadelphia, PA 19108
Phone: (215) 351-1099
Fax: (215) 451-2045
[EMAIL PROTECTED]
___________________________________________
Keeping People and Information Connected (TM)
http://www.availability.sungard.com
"Zimelis, Martin
A"
<[EMAIL PROTECTED] To
a.com> [email protected]
Sent by: VM/ESA cc
and z/VM
Discussions Subject
<[EMAIL PROTECTED] Re: Module/TEXT deck size (was VM
.UARK.EDU> maclib reference
01/12/2006 02:52
PM
Please respond to
VM/ESA and z/VM
Discussions
<[EMAIL PROTECTED]
.UARK.EDU>
Steve,
I don't believe there's a macro or DIAG, but, for a MODULE file, read
the first record and subtract the second word from the third word. For
TEXT decks, I don't think it's that straightforward.
Marty
______________________________
Marty Zimelis
Senior Consultant
CA
mailto:[EMAIL PROTECTED]
voice: +1.703.708.3236
fax: +1.703.708.3267
-----Original Message-----
From: VM/ESA and z/VM Discussions [mailto:[EMAIL PROTECTED]
Behalf Of Steve Gentry
Sent: Thursday, January 12, 2006 2:27 PM
To: [email protected]
Subject: Re: VM maclib reference
New program, mode'ing old ones. This is the one I asked about last
week, regarding example about loading table(s) above 16m line.
Looks like CMSSTOR, in part, will help. Is there a macro or DIAG
to tell me the length(size) in bytes of a module? What about a TEXT
deck?
This has to be able to be done in an assembler pgm.
Steve
Alan Altmark <[EMAIL PROTECTED]>
Sent by: VM/ESA and z/VM Discussions To:
<[email protected]> [email protected]
cc:
Subject:
01/12/2006 01:14 PM Re: VM maclib reference
Please respond to VM/ESA and z/VM
Discussions
On Thursday, 01/12/2006 at 11:57 EST, Steve Gentry
<[EMAIL PROTECTED]> wrote:
> Thanks to those who have replied. I know how difficult it is to
find
doc on
> some of these macros.
For system services macros, use the "z/OS MVS Programming
[Authorized]
Assembler Services Reference". (Most of the macros you'll want are
not
APF Authorized.) The data management macros are in "DFSMS Macro
Instructions for Data Sets".
If this program is going to be run on z/OS, do your assemblies on
z/OS,
not CMS, and ignore the CMS books. If you're going to run it on CMS,
why
convert the macros? If absolutely necessary, then make sure you use
only
the macro parameters described in the CMS ADG for Assembler and obey
any
other restrictions mentioned therein.
Alan Altmark
z/VM Development
IBM Endicott
