Re: Size of the Writable Static Area
It is re-entrant have the Rent option and I have global areas Thanks > On Dec 24, 2020, at 11:30 AM, Joe Monk wrote: > > OK so there's no need for reentrancy. Thus, no need for WSA. > > Joe > >> On Thu, Dec 24, 2020 at 10:29 AM Joseph Reichman >> wrote: >> >> It’s a batch program called from a started task >> >> >> >>>> On Dec 24, 2020, at 11:18 AM, Joe Monk wrote: >>> >>> Still not sure why you have a WSA... Youre not using CICS, right? >>> >>> Joe >>> >>>> On Thu, Dec 24, 2020 at 10:11 AM Joseph Reichman >> >>>> wrote: >>>> >>>> This code is right after my prologue >>>> >>>> >>>> ST0,#WSA_1 >>>> >>>> So I have to somehow make sure that register 0 has the right value >>>> >>>> Thanks >>>> >>>> -Original Message- >>>> From: IBM Mainframe Discussion List On >> Behalf >>>> Of Joe Monk >>>> Sent: Thursday, December 24, 2020 11:04 AM >>>> To: IBM-MAIN@LISTSERV.UA.EDU >>>> Subject: Re: Size of the Writable Static Area >>>> >>>> OK but I dont think you need a WSA. >>>> >>>> Joe >>>> >>>> On Thu, Dec 24, 2020 at 10:00 AM Joseph Reichman >> >>>> wrote: >>>> >>>>> Thanks I think the problem is my main program is called OPENFILE In >>>>> this program I load sysadata to a dataspace >>>>> >>>>> Why did I use metal C because I have similar C code in windows and >>>>> thought with #pragma if __MVS I could save coding I found it easier to >>>>> work with Metal then LE as it gives me more options >>>>> >>>>> I think some where there is a way to have alternate main name I think >>>>> I have to follow that path >>>>> >>>>> >>>>>> On Dec 24, 2020, at 10:46 AM, Joe Monk wrote: >>>>>> >>>>>> No. If you are calling METAL C from assembler, METAL C will take >>>>>> care >>>>> of >>>>>> the WSA... >>>>>> >>>>>> "The RENT environment initialization and termination routines are >>>>>> called >>>>> to >>>>>> establish and terminate the dynamically allocated WSA storage with >>>>>> the static initialization data applied. For the AMODE 31 "main" >>>>>> function, CCNZINIT and CCNZTERM are the names of these routines. >>>>>> While for the >>>>> AMODE >>>>>> 64 "main" function, CCNZQINI and CCNZQTRM are the function names ... >>>>>> The actual WSA storage management is done by user supplied plug-in >>>>>> routines called from CCNZINIT and CCNZTERM." >>>>>> >>>>>> Joe >>>>>> >>>>>>> On Thu, Dec 24, 2020 at 9:42 AM Joseph Reichman >>>>>>> >>>>>>> wrote: >>>>>>> >>>>>>> Just read it FYI I am Calling Metal C from Assembler (via Link) Me >>>>> thinks >>>>>>> I have to init The WSA area Binyamin Dessin suggested I use a CXD >>>>> variable >>>>>>> to get the size of the WSA >>>>>>> >>>>>>> -Original Message- >>>>>>> From: IBM Mainframe Discussion List On >>>>> Behalf >>>>>>> Of Joe Monk >>>>>>> Sent: Thursday, December 24, 2020 10:01 AM >>>>>>> To: IBM-MAIN@LISTSERV.UA.EDU >>>>>>> Subject: Re: Size of the Writable Static Area >>>>>>> >>>>>>> Check page 31 in this: >>>>>>> >>>>>>> >>>>> https://www-01.ibm.com/servers/resourcelink/svc00100.nsf/pages/zosv2r3 >>>>> sc147313/$file/ccrug00_v2r3.pdf >>>>>>> >>>>>>> Joe >>>>>>> >>>>>>> On Thu, Dec 24, 2020 at 8:39 AM Joseph Reichman >>>>>>> >>>>>>> wrote: >>>>>>> >>>>>>>> I’m writing a prolog for a metal C program I noticed that after &
Re: Size of the Writable Static Area
OK so there's no need for reentrancy. Thus, no need for WSA. Joe On Thu, Dec 24, 2020 at 10:29 AM Joseph Reichman wrote: > It’s a batch program called from a started task > > > > > On Dec 24, 2020, at 11:18 AM, Joe Monk wrote: > > > > Still not sure why you have a WSA... Youre not using CICS, right? > > > > Joe > > > >> On Thu, Dec 24, 2020 at 10:11 AM Joseph Reichman > > >> wrote: > >> > >> This code is right after my prologue > >> > >> > >>ST0,#WSA_1 > >> > >> So I have to somehow make sure that register 0 has the right value > >> > >> Thanks > >> > >> -Original Message- > >> From: IBM Mainframe Discussion List On > Behalf > >> Of Joe Monk > >> Sent: Thursday, December 24, 2020 11:04 AM > >> To: IBM-MAIN@LISTSERV.UA.EDU > >> Subject: Re: Size of the Writable Static Area > >> > >> OK but I dont think you need a WSA. > >> > >> Joe > >> > >> On Thu, Dec 24, 2020 at 10:00 AM Joseph Reichman > > >> wrote: > >> > >>> Thanks I think the problem is my main program is called OPENFILE In > >>> this program I load sysadata to a dataspace > >>> > >>> Why did I use metal C because I have similar C code in windows and > >>> thought with #pragma if __MVS I could save coding I found it easier to > >>> work with Metal then LE as it gives me more options > >>> > >>> I think some where there is a way to have alternate main name I think > >>> I have to follow that path > >>> > >>> > >>>> On Dec 24, 2020, at 10:46 AM, Joe Monk wrote: > >>>> > >>>> No. If you are calling METAL C from assembler, METAL C will take > >>>> care > >>> of > >>>> the WSA... > >>>> > >>>> "The RENT environment initialization and termination routines are > >>>> called > >>> to > >>>> establish and terminate the dynamically allocated WSA storage with > >>>> the static initialization data applied. For the AMODE 31 "main" > >>>> function, CCNZINIT and CCNZTERM are the names of these routines. > >>>> While for the > >>> AMODE > >>>> 64 "main" function, CCNZQINI and CCNZQTRM are the function names ... > >>>> The actual WSA storage management is done by user supplied plug-in > >>>> routines called from CCNZINIT and CCNZTERM." > >>>> > >>>> Joe > >>>> > >>>>> On Thu, Dec 24, 2020 at 9:42 AM Joseph Reichman > >>>>> > >>>>> wrote: > >>>>> > >>>>> Just read it FYI I am Calling Metal C from Assembler (via Link) Me > >>> thinks > >>>>> I have to init The WSA area Binyamin Dessin suggested I use a CXD > >>> variable > >>>>> to get the size of the WSA > >>>>> > >>>>> -Original Message- > >>>>> From: IBM Mainframe Discussion List On > >>> Behalf > >>>>> Of Joe Monk > >>>>> Sent: Thursday, December 24, 2020 10:01 AM > >>>>> To: IBM-MAIN@LISTSERV.UA.EDU > >>>>> Subject: Re: Size of the Writable Static Area > >>>>> > >>>>> Check page 31 in this: > >>>>> > >>>>> > >>> https://www-01.ibm.com/servers/resourcelink/svc00100.nsf/pages/zosv2r3 > >>> sc147313/$file/ccrug00_v2r3.pdf > >>>>> > >>>>> Joe > >>>>> > >>>>> On Thu, Dec 24, 2020 at 8:39 AM Joseph Reichman > >>>>> > >>>>> wrote: > >>>>> > >>>>>> I’m writing a prolog for a metal C program I noticed that after > >>>>>> the prolog code Registers 0 is stored in #WSA_1 seems like storage > >>>>>> has to be allocated for it ( writable static area ) in addition to > >>>>>> the dynamic storage ( register save + auto variables ) > >>>>>> > >>>>>> > >>>>>>> On Dec 24, 2020, at 9:32 AM, Peter Relson > >> wrote: > >>>>>>> > >>>>>>> I think of the writeable static area as an area that LE > >>>>
Re: Size of the Writable Static Area
It’s a batch program called from a started task > On Dec 24, 2020, at 11:18 AM, Joe Monk wrote: > > Still not sure why you have a WSA... Youre not using CICS, right? > > Joe > >> On Thu, Dec 24, 2020 at 10:11 AM Joseph Reichman >> wrote: >> >> This code is right after my prologue >> >> >>ST0,#WSA_1 >> >> So I have to somehow make sure that register 0 has the right value >> >> Thanks >> >> -Original Message- >> From: IBM Mainframe Discussion List On Behalf >> Of Joe Monk >> Sent: Thursday, December 24, 2020 11:04 AM >> To: IBM-MAIN@LISTSERV.UA.EDU >> Subject: Re: Size of the Writable Static Area >> >> OK but I dont think you need a WSA. >> >> Joe >> >> On Thu, Dec 24, 2020 at 10:00 AM Joseph Reichman >> wrote: >> >>> Thanks I think the problem is my main program is called OPENFILE In >>> this program I load sysadata to a dataspace >>> >>> Why did I use metal C because I have similar C code in windows and >>> thought with #pragma if __MVS I could save coding I found it easier to >>> work with Metal then LE as it gives me more options >>> >>> I think some where there is a way to have alternate main name I think >>> I have to follow that path >>> >>> >>>> On Dec 24, 2020, at 10:46 AM, Joe Monk wrote: >>>> >>>> No. If you are calling METAL C from assembler, METAL C will take >>>> care >>> of >>>> the WSA... >>>> >>>> "The RENT environment initialization and termination routines are >>>> called >>> to >>>> establish and terminate the dynamically allocated WSA storage with >>>> the static initialization data applied. For the AMODE 31 "main" >>>> function, CCNZINIT and CCNZTERM are the names of these routines. >>>> While for the >>> AMODE >>>> 64 "main" function, CCNZQINI and CCNZQTRM are the function names ... >>>> The actual WSA storage management is done by user supplied plug-in >>>> routines called from CCNZINIT and CCNZTERM." >>>> >>>> Joe >>>> >>>>> On Thu, Dec 24, 2020 at 9:42 AM Joseph Reichman >>>>> >>>>> wrote: >>>>> >>>>> Just read it FYI I am Calling Metal C from Assembler (via Link) Me >>> thinks >>>>> I have to init The WSA area Binyamin Dessin suggested I use a CXD >>> variable >>>>> to get the size of the WSA >>>>> >>>>> -Original Message- >>>>> From: IBM Mainframe Discussion List On >>> Behalf >>>>> Of Joe Monk >>>>> Sent: Thursday, December 24, 2020 10:01 AM >>>>> To: IBM-MAIN@LISTSERV.UA.EDU >>>>> Subject: Re: Size of the Writable Static Area >>>>> >>>>> Check page 31 in this: >>>>> >>>>> >>> https://www-01.ibm.com/servers/resourcelink/svc00100.nsf/pages/zosv2r3 >>> sc147313/$file/ccrug00_v2r3.pdf >>>>> >>>>> Joe >>>>> >>>>> On Thu, Dec 24, 2020 at 8:39 AM Joseph Reichman >>>>> >>>>> wrote: >>>>> >>>>>> I’m writing a prolog for a metal C program I noticed that after >>>>>> the prolog code Registers 0 is stored in #WSA_1 seems like storage >>>>>> has to be allocated for it ( writable static area ) in addition to >>>>>> the dynamic storage ( register save + auto variables ) >>>>>> >>>>>> >>>>>>> On Dec 24, 2020, at 9:32 AM, Peter Relson >> wrote: >>>>>>> >>>>>>> I think of the writeable static area as an area that LE >>>>>>> instantiates on your behalf. >>>>>>> As far as I know, there is no interface provided by which you can >>>>>>> do >>>>>> this. >>>>>>> >>>>>>> If LE is going to do this for you, using loader services that >>>>>>> rely on information within the program object itself (and there >>>>>>> is such information), how is knowing the size of the area of help >> to you? >>>>>>> >>>>>>> Peter Relson >>>>>>> z/OS Core Technology Design >>>>>&g
Re: Size of the Writable Static Area
Still not sure why you have a WSA... Youre not using CICS, right? Joe On Thu, Dec 24, 2020 at 10:11 AM Joseph Reichman wrote: > This code is right after my prologue > > > ST0,#WSA_1 > > So I have to somehow make sure that register 0 has the right value > > Thanks > > -Original Message- > From: IBM Mainframe Discussion List On Behalf > Of Joe Monk > Sent: Thursday, December 24, 2020 11:04 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Size of the Writable Static Area > > OK but I dont think you need a WSA. > > Joe > > On Thu, Dec 24, 2020 at 10:00 AM Joseph Reichman > wrote: > > > Thanks I think the problem is my main program is called OPENFILE In > > this program I load sysadata to a dataspace > > > > Why did I use metal C because I have similar C code in windows and > > thought with #pragma if __MVS I could save coding I found it easier to > > work with Metal then LE as it gives me more options > > > > I think some where there is a way to have alternate main name I think > > I have to follow that path > > > > > > > On Dec 24, 2020, at 10:46 AM, Joe Monk wrote: > > > > > > No. If you are calling METAL C from assembler, METAL C will take > > > care > > of > > > the WSA... > > > > > > "The RENT environment initialization and termination routines are > > > called > > to > > > establish and terminate the dynamically allocated WSA storage with > > > the static initialization data applied. For the AMODE 31 "main" > > > function, CCNZINIT and CCNZTERM are the names of these routines. > > > While for the > > AMODE > > > 64 "main" function, CCNZQINI and CCNZQTRM are the function names ... > > > The actual WSA storage management is done by user supplied plug-in > > > routines called from CCNZINIT and CCNZTERM." > > > > > > Joe > > > > > >> On Thu, Dec 24, 2020 at 9:42 AM Joseph Reichman > > >> > > >> wrote: > > >> > > >> Just read it FYI I am Calling Metal C from Assembler (via Link) Me > > thinks > > >> I have to init The WSA area Binyamin Dessin suggested I use a CXD > > variable > > >> to get the size of the WSA > > >> > > >> -Original Message- > > >> From: IBM Mainframe Discussion List On > > Behalf > > >> Of Joe Monk > > >> Sent: Thursday, December 24, 2020 10:01 AM > > >> To: IBM-MAIN@LISTSERV.UA.EDU > > >> Subject: Re: Size of the Writable Static Area > > >> > > >> Check page 31 in this: > > >> > > >> > > https://www-01.ibm.com/servers/resourcelink/svc00100.nsf/pages/zosv2r3 > > sc147313/$file/ccrug00_v2r3.pdf > > >> > > >> Joe > > >> > > >> On Thu, Dec 24, 2020 at 8:39 AM Joseph Reichman > > >> > > >> wrote: > > >> > > >>> I’m writing a prolog for a metal C program I noticed that after > > >>> the prolog code Registers 0 is stored in #WSA_1 seems like storage > > >>> has to be allocated for it ( writable static area ) in addition to > > >>> the dynamic storage ( register save + auto variables ) > > >>> > > >>> > > >>>> On Dec 24, 2020, at 9:32 AM, Peter Relson > wrote: > > >>>> > > >>>> I think of the writeable static area as an area that LE > > >>>> instantiates on your behalf. > > >>>> As far as I know, there is no interface provided by which you can > > >>>> do > > >>> this. > > >>>> > > >>>> If LE is going to do this for you, using loader services that > > >>>> rely on information within the program object itself (and there > > >>>> is such information), how is knowing the size of the area of help > to you? > > >>>> > > >>>> Peter Relson > > >>>> z/OS Core Technology Design > > >>>> > > >>>> > > >>>> - > > >>>> --- > > >>>> -- For IBM-MAIN subscribe / signoff / archive access > > >>>> instructions, send email to lists...@listserv.ua.edu with the > > >>>> message: INFO IBM-MAIN > > >>> > > >>>
Re: Size of the Writable Static Area
This code is right after my prologue ST0,#WSA_1 So I have to somehow make sure that register 0 has the right value Thanks -Original Message- From: IBM Mainframe Discussion List On Behalf Of Joe Monk Sent: Thursday, December 24, 2020 11:04 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Size of the Writable Static Area OK but I dont think you need a WSA. Joe On Thu, Dec 24, 2020 at 10:00 AM Joseph Reichman wrote: > Thanks I think the problem is my main program is called OPENFILE In > this program I load sysadata to a dataspace > > Why did I use metal C because I have similar C code in windows and > thought with #pragma if __MVS I could save coding I found it easier to > work with Metal then LE as it gives me more options > > I think some where there is a way to have alternate main name I think > I have to follow that path > > > > On Dec 24, 2020, at 10:46 AM, Joe Monk wrote: > > > > No. If you are calling METAL C from assembler, METAL C will take > > care > of > > the WSA... > > > > "The RENT environment initialization and termination routines are > > called > to > > establish and terminate the dynamically allocated WSA storage with > > the static initialization data applied. For the AMODE 31 "main" > > function, CCNZINIT and CCNZTERM are the names of these routines. > > While for the > AMODE > > 64 "main" function, CCNZQINI and CCNZQTRM are the function names ... > > The actual WSA storage management is done by user supplied plug-in > > routines called from CCNZINIT and CCNZTERM." > > > > Joe > > > >> On Thu, Dec 24, 2020 at 9:42 AM Joseph Reichman > >> > >> wrote: > >> > >> Just read it FYI I am Calling Metal C from Assembler (via Link) Me > thinks > >> I have to init The WSA area Binyamin Dessin suggested I use a CXD > variable > >> to get the size of the WSA > >> > >> -Original Message- > >> From: IBM Mainframe Discussion List On > Behalf > >> Of Joe Monk > >> Sent: Thursday, December 24, 2020 10:01 AM > >> To: IBM-MAIN@LISTSERV.UA.EDU > >> Subject: Re: Size of the Writable Static Area > >> > >> Check page 31 in this: > >> > >> > https://www-01.ibm.com/servers/resourcelink/svc00100.nsf/pages/zosv2r3 > sc147313/$file/ccrug00_v2r3.pdf > >> > >> Joe > >> > >> On Thu, Dec 24, 2020 at 8:39 AM Joseph Reichman > >> > >> wrote: > >> > >>> I’m writing a prolog for a metal C program I noticed that after > >>> the prolog code Registers 0 is stored in #WSA_1 seems like storage > >>> has to be allocated for it ( writable static area ) in addition to > >>> the dynamic storage ( register save + auto variables ) > >>> > >>> > >>>> On Dec 24, 2020, at 9:32 AM, Peter Relson wrote: > >>>> > >>>> I think of the writeable static area as an area that LE > >>>> instantiates on your behalf. > >>>> As far as I know, there is no interface provided by which you can > >>>> do > >>> this. > >>>> > >>>> If LE is going to do this for you, using loader services that > >>>> rely on information within the program object itself (and there > >>>> is such information), how is knowing the size of the area of help to you? > >>>> > >>>> Peter Relson > >>>> z/OS Core Technology Design > >>>> > >>>> > >>>> - > >>>> --- > >>>> -- For IBM-MAIN subscribe / signoff / archive access > >>>> instructions, send email to lists...@listserv.ua.edu with the > >>>> message: INFO IBM-MAIN > >>> > >>> -- > >>> For IBM-MAIN subscribe / signoff / archive access > >>> instructions, send email to lists...@listserv.ua.edu with the > >>> message: INFO IBM-MAIN > >>> > >> > >> --- > >> --- For IBM-MAIN subscribe / signoff / archive access instructions, > >> send > email > >> to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > >> > >> --- > >> --- For IBM-MAIN subscribe / signoff / archive acc
Re: Size of the Writable Static Area
OK but I dont think you need a WSA. Joe On Thu, Dec 24, 2020 at 10:00 AM Joseph Reichman wrote: > Thanks I think the problem is my main program is called OPENFILE In this > program I load sysadata to a dataspace > > Why did I use metal C because I have similar C code in windows and thought > with #pragma if __MVS I could save coding I found it easier to work with > Metal then LE as it gives me more options > > I think some where there is a way to have alternate main name I think I > have to follow that path > > > > On Dec 24, 2020, at 10:46 AM, Joe Monk wrote: > > > > No. If you are calling METAL C from assembler, METAL C will take care > of > > the WSA... > > > > "The RENT environment initialization and termination routines are called > to > > establish and terminate the dynamically allocated WSA storage with the > > static initialization data applied. For the AMODE 31 "main" function, > > CCNZINIT and CCNZTERM are the names of these routines. While for the > AMODE > > 64 "main" function, CCNZQINI and CCNZQTRM are the function names ... The > > actual WSA storage management is done by user supplied plug-in routines > > called from CCNZINIT and CCNZTERM." > > > > Joe > > > >> On Thu, Dec 24, 2020 at 9:42 AM Joseph Reichman > >> wrote: > >> > >> Just read it FYI I am Calling Metal C from Assembler (via Link) Me > thinks > >> I have to init The WSA area Binyamin Dessin suggested I use a CXD > variable > >> to get the size of the WSA > >> > >> -Original Message- > >> From: IBM Mainframe Discussion List On > Behalf > >> Of Joe Monk > >> Sent: Thursday, December 24, 2020 10:01 AM > >> To: IBM-MAIN@LISTSERV.UA.EDU > >> Subject: Re: Size of the Writable Static Area > >> > >> Check page 31 in this: > >> > >> > https://www-01.ibm.com/servers/resourcelink/svc00100.nsf/pages/zosv2r3sc147313/$file/ccrug00_v2r3.pdf > >> > >> Joe > >> > >> On Thu, Dec 24, 2020 at 8:39 AM Joseph Reichman > >> wrote: > >> > >>> I’m writing a prolog for a metal C program I noticed that after the > >>> prolog code Registers 0 is stored in #WSA_1 seems like storage has to > >>> be allocated for it ( writable static area ) in addition to the > >>> dynamic storage ( register save + auto variables ) > >>> > >>> > >>>> On Dec 24, 2020, at 9:32 AM, Peter Relson wrote: > >>>> > >>>> I think of the writeable static area as an area that LE > >>>> instantiates on your behalf. > >>>> As far as I know, there is no interface provided by which you can do > >>> this. > >>>> > >>>> If LE is going to do this for you, using loader services that rely > >>>> on information within the program object itself (and there is such > >>>> information), how is knowing the size of the area of help to you? > >>>> > >>>> Peter Relson > >>>> z/OS Core Technology Design > >>>> > >>>> > >>>> > >>>> -- For IBM-MAIN subscribe / signoff / archive access instructions, > >>>> send email to lists...@listserv.ua.edu with the message: INFO > >>>> IBM-MAIN > >>> > >>> -- > >>> For IBM-MAIN subscribe / signoff / archive access instructions, send > >>> email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > >>> > >> > >> -- > >> For IBM-MAIN subscribe / signoff / archive access instructions, send > email > >> to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > >> > >> -- > >> For IBM-MAIN subscribe / signoff / archive access instructions, > >> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > >> > > > > -- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Size of the Writable Static Area
Thanks I think the problem is my main program is called OPENFILE In this program I load sysadata to a dataspace Why did I use metal C because I have similar C code in windows and thought with #pragma if __MVS I could save coding I found it easier to work with Metal then LE as it gives me more options I think some where there is a way to have alternate main name I think I have to follow that path > On Dec 24, 2020, at 10:46 AM, Joe Monk wrote: > > No. If you are calling METAL C from assembler, METAL C will take care of > the WSA... > > "The RENT environment initialization and termination routines are called to > establish and terminate the dynamically allocated WSA storage with the > static initialization data applied. For the AMODE 31 "main" function, > CCNZINIT and CCNZTERM are the names of these routines. While for the AMODE > 64 "main" function, CCNZQINI and CCNZQTRM are the function names ... The > actual WSA storage management is done by user supplied plug-in routines > called from CCNZINIT and CCNZTERM." > > Joe > >> On Thu, Dec 24, 2020 at 9:42 AM Joseph Reichman >> wrote: >> >> Just read it FYI I am Calling Metal C from Assembler (via Link) Me thinks >> I have to init The WSA area Binyamin Dessin suggested I use a CXD variable >> to get the size of the WSA >> >> -Original Message- >> From: IBM Mainframe Discussion List On Behalf >> Of Joe Monk >> Sent: Thursday, December 24, 2020 10:01 AM >> To: IBM-MAIN@LISTSERV.UA.EDU >> Subject: Re: Size of the Writable Static Area >> >> Check page 31 in this: >> >> https://www-01.ibm.com/servers/resourcelink/svc00100.nsf/pages/zosv2r3sc147313/$file/ccrug00_v2r3.pdf >> >> Joe >> >> On Thu, Dec 24, 2020 at 8:39 AM Joseph Reichman >> wrote: >> >>> I’m writing a prolog for a metal C program I noticed that after the >>> prolog code Registers 0 is stored in #WSA_1 seems like storage has to >>> be allocated for it ( writable static area ) in addition to the >>> dynamic storage ( register save + auto variables ) >>> >>> >>>> On Dec 24, 2020, at 9:32 AM, Peter Relson wrote: >>>> >>>> I think of the writeable static area as an area that LE >>>> instantiates on your behalf. >>>> As far as I know, there is no interface provided by which you can do >>> this. >>>> >>>> If LE is going to do this for you, using loader services that rely >>>> on information within the program object itself (and there is such >>>> information), how is knowing the size of the area of help to you? >>>> >>>> Peter Relson >>>> z/OS Core Technology Design >>>> >>>> >>>> >>>> -- For IBM-MAIN subscribe / signoff / archive access instructions, >>>> send email to lists...@listserv.ua.edu with the message: INFO >>>> IBM-MAIN >>> >>> -- >>> For IBM-MAIN subscribe / signoff / archive access instructions, send >>> email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN >>> >> >> -- >> For IBM-MAIN subscribe / signoff / archive access instructions, send email >> to lists...@listserv.ua.edu with the message: INFO IBM-MAIN >> >> -- >> For IBM-MAIN subscribe / signoff / archive access instructions, >> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN >> > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Size of the Writable Static Area
No. If you are calling METAL C from assembler, METAL C will take care of the WSA... "The RENT environment initialization and termination routines are called to establish and terminate the dynamically allocated WSA storage with the static initialization data applied. For the AMODE 31 "main" function, CCNZINIT and CCNZTERM are the names of these routines. While for the AMODE 64 "main" function, CCNZQINI and CCNZQTRM are the function names ... The actual WSA storage management is done by user supplied plug-in routines called from CCNZINIT and CCNZTERM." Joe On Thu, Dec 24, 2020 at 9:42 AM Joseph Reichman wrote: > Just read it FYI I am Calling Metal C from Assembler (via Link) Me thinks > I have to init The WSA area Binyamin Dessin suggested I use a CXD variable > to get the size of the WSA > > -Original Message- > From: IBM Mainframe Discussion List On Behalf > Of Joe Monk > Sent: Thursday, December 24, 2020 10:01 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Size of the Writable Static Area > > Check page 31 in this: > > https://www-01.ibm.com/servers/resourcelink/svc00100.nsf/pages/zosv2r3sc147313/$file/ccrug00_v2r3.pdf > > Joe > > On Thu, Dec 24, 2020 at 8:39 AM Joseph Reichman > wrote: > > > I’m writing a prolog for a metal C program I noticed that after the > > prolog code Registers 0 is stored in #WSA_1 seems like storage has to > > be allocated for it ( writable static area ) in addition to the > > dynamic storage ( register save + auto variables ) > > > > > > > On Dec 24, 2020, at 9:32 AM, Peter Relson wrote: > > > > > > I think of the writeable static area as an area that LE > > > instantiates on your behalf. > > > As far as I know, there is no interface provided by which you can do > > this. > > > > > > If LE is going to do this for you, using loader services that rely > > > on information within the program object itself (and there is such > > > information), how is knowing the size of the area of help to you? > > > > > > Peter Relson > > > z/OS Core Technology Design > > > > > > > > > > > > -- For IBM-MAIN subscribe / signoff / archive access instructions, > > > send email to lists...@listserv.ua.edu with the message: INFO > > > IBM-MAIN > > > > -- > > For IBM-MAIN subscribe / signoff / archive access instructions, send > > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, send email > to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Size of the Writable Static Area
Just read it FYI I am Calling Metal C from Assembler (via Link) Me thinks I have to init The WSA area Binyamin Dessin suggested I use a CXD variable to get the size of the WSA -Original Message- From: IBM Mainframe Discussion List On Behalf Of Joe Monk Sent: Thursday, December 24, 2020 10:01 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Size of the Writable Static Area Check page 31 in this: https://www-01.ibm.com/servers/resourcelink/svc00100.nsf/pages/zosv2r3sc147313/$file/ccrug00_v2r3.pdf Joe On Thu, Dec 24, 2020 at 8:39 AM Joseph Reichman wrote: > I’m writing a prolog for a metal C program I noticed that after the > prolog code Registers 0 is stored in #WSA_1 seems like storage has to > be allocated for it ( writable static area ) in addition to the > dynamic storage ( register save + auto variables ) > > > > On Dec 24, 2020, at 9:32 AM, Peter Relson wrote: > > > > I think of the writeable static area as an area that LE > > instantiates on your behalf. > > As far as I know, there is no interface provided by which you can do > this. > > > > If LE is going to do this for you, using loader services that rely > > on information within the program object itself (and there is such > > information), how is knowing the size of the area of help to you? > > > > Peter Relson > > z/OS Core Technology Design > > > > > > > > -- For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to lists...@listserv.ua.edu with the message: INFO > > IBM-MAIN > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Size of the Writable Static Area
This is the code after the prolog don’t see a call WSA initialization + LR0,2 + DROP 15 @@BGN@1 DS0H AIF (NOT _SASIG).@@NOSIG1 LLILH 11,X'C6F7' OILL 11,X'E2C1' ST11,4(,13) 5 AIF (_NAB_STORED).@@NONAB1 6 LA11,720 7 ALR 11,13 "IBMUSER.DBGR.SERVER(OPENFILE)" t Source Statement 8 ST11,#NAB_1-@@AUTO@1+4(,13) 9 MVHI #NAB_1-@@AUTO@1(13),0 0 .@@NONAB1 ANOP 1 USING @@AUTO@1,13 2 LARL 3,@@LIT@1 3 LAE 3,0(3) 4 USING @@LIT@1,3 5 ST0,#WSA_1 <=== 6 STAM 1,1,336(13) #SR 7 ST1,332(,13) #SR 8 LAE 14,0(14,0) 9 STAM 14,14,712(13) #ar -Original Message- From: IBM Mainframe Discussion List On Behalf Of Joe Monk Sent: Thursday, December 24, 2020 10:01 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Size of the Writable Static Area Check page 31 in this: https://www-01.ibm.com/servers/resourcelink/svc00100.nsf/pages/zosv2r3sc147313/$file/ccrug00_v2r3.pdf Joe On Thu, Dec 24, 2020 at 8:39 AM Joseph Reichman wrote: > I’m writing a prolog for a metal C program I noticed that after the > prolog code Registers 0 is stored in #WSA_1 seems like storage has to > be allocated for it ( writable static area ) in addition to the > dynamic storage ( register save + auto variables ) > > > > On Dec 24, 2020, at 9:32 AM, Peter Relson wrote: > > > > I think of the writeable static area as an area that LE > > instantiates on your behalf. > > As far as I know, there is no interface provided by which you can do > this. > > > > If LE is going to do this for you, using loader services that rely > > on information within the program object itself (and there is such > > information), how is knowing the size of the area of help to you? > > > > Peter Relson > > z/OS Core Technology Design > > > > > > > > -- For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to lists...@listserv.ua.edu with the message: INFO > > IBM-MAIN > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Size of the Writable Static Area
Check page 31 in this: https://www-01.ibm.com/servers/resourcelink/svc00100.nsf/pages/zosv2r3sc147313/$file/ccrug00_v2r3.pdf Joe On Thu, Dec 24, 2020 at 8:39 AM Joseph Reichman wrote: > I’m writing a prolog for a metal C program > I noticed that after the prolog code > Registers 0 is stored in #WSA_1 seems like storage has to be allocated for > it ( writable static area ) in addition to the dynamic storage ( register > save + auto variables ) > > > > On Dec 24, 2020, at 9:32 AM, Peter Relson wrote: > > > > I think of the writeable static area as an area that LE instantiates on > > your behalf. > > As far as I know, there is no interface provided by which you can do > this. > > > > If LE is going to do this for you, using loader services that rely on > > information within the program object itself (and there is such > > information), how is knowing the size of the area of help to you? > > > > Peter Relson > > z/OS Core Technology Design > > > > > > -- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Size of the Writable Static Area
GPR 0 is used to pass the address of the WSA. If youre writing a prolog for a Metal C program, you dont need to worry about the size of the WSA unless you plan to do something with it. The Metal C program should call the WSA init and term upon entry and exit on its own. Joe On Thu, Dec 24, 2020 at 8:39 AM Joseph Reichman wrote: > I’m writing a prolog for a metal C program > I noticed that after the prolog code > Registers 0 is stored in #WSA_1 seems like storage has to be allocated for > it ( writable static area ) in addition to the dynamic storage ( register > save + auto variables ) > > > > On Dec 24, 2020, at 9:32 AM, Peter Relson wrote: > > > > I think of the writeable static area as an area that LE instantiates on > > your behalf. > > As far as I know, there is no interface provided by which you can do > this. > > > > If LE is going to do this for you, using loader services that rely on > > information within the program object itself (and there is such > > information), how is knowing the size of the area of help to you? > > > > Peter Relson > > z/OS Core Technology Design > > > > > > -- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Size of the Writable Static Area
I’m writing a prolog for a metal C program I noticed that after the prolog code Registers 0 is stored in #WSA_1 seems like storage has to be allocated for it ( writable static area ) in addition to the dynamic storage ( register save + auto variables ) > On Dec 24, 2020, at 9:32 AM, Peter Relson wrote: > > I think of the writeable static area as an area that LE instantiates on > your behalf. > As far as I know, there is no interface provided by which you can do this. > > If LE is going to do this for you, using loader services that rely on > information within the program object itself (and there is such > information), how is knowing the size of the area of help to you? > > Peter Relson > z/OS Core Technology Design > > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Size of the Writable Static Area
I think of the writeable static area as an area that LE instantiates on your behalf. As far as I know, there is no interface provided by which you can do this. If LE is going to do this for you, using loader services that rely on information within the program object itself (and there is such information), how is knowing the size of the area of help to you? Peter Relson z/OS Core Technology Design -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Size of the Writable Static Area
Binyamin Thanks for your help I saw your e-mail right away spent a lot of time in the HLASM program and language looking up the usage of DXD / CXD Seems to me the writable static area is in the class specified by CATTR I did a lot of reading on CATTR seems like that's is a way of defining a part That lives in a class specified by the CATTR. Are those items in the class part of an external dummy section DXD I understand that the symbol where the CXD is defined is full word whose value initialized by the binder of all the external dummy sections is the parts defined by class from the CATTR part of that value thanks -Original Message- From: IBM Mainframe Discussion List On Behalf Of Binyamin Dissen Sent: Wednesday, December 23, 2020 2:48 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Size of the Writable Static Area DXD / CXD On Wed, 23 Dec 2020 11:37:29 -0500 Joseph Reichman wrote: :>I am writing my own prolog code (Metal C ). From the GBL.. Global variables :>produced by the complier I determine the size of the automatic variables :>Register save area etc. So That I can determine how much Dynamic Storage I :>need :>I am wondering is there any way to determine the size of the writable static :>area -- Binyamin Dissen http://www.dissensoftware.com Director, Dissen Software, Bar & Grill - Israel Should you use the mailblocks package and expect a response from me, you should preauthorize the dissensoftware.com domain. I very rarely bother responding to challenge/response systems, especially those from irresponsible companies. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Size of the Writable Static Area
DXD / CXD On Wed, 23 Dec 2020 11:37:29 -0500 Joseph Reichman wrote: :>I am writing my own prolog code (Metal C ). From the GBL.. Global variables :>produced by the complier I determine the size of the automatic variables :>Register save area etc. So That I can determine how much Dynamic Storage I :>need :>I am wondering is there any way to determine the size of the writable static :>area -- Binyamin Dissen http://www.dissensoftware.com Director, Dissen Software, Bar & Grill - Israel Should you use the mailblocks package and expect a response from me, you should preauthorize the dissensoftware.com domain. I very rarely bother responding to challenge/response systems, especially those from irresponsible companies. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Size of the Writable Static Area
Hi I am writing my own prolog code (Metal C ). From the GBL.. Global variables produced by the complier I determine the size of the automatic variables Register save area etc. So That I can determine how much Dynamic Storage I need I am wondering is there any way to determine the size of the writable static area Thanks -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
