[Info-vax] Calling $CREPRC in COBOL

[Richard Maher]

On 20/06/2022 10:20 am, Dave Froble wrote:
> On 6/10/2022 4:34 PM, Craig A. Berry wrote:
>> 
>> On 6/10/22 2:57 PM, Bill Gunshannon wrote:
>>> On 6/10/22 15:03, Craig A. Berry wrote:
>>>> 
>>>> On 6/10/22 1:27 PM, Bill Gunshannon wrote:
>>>>> On 6/10/22 14:16, Craig A. Berry wrote:
>>>>>> On 6/10/22 12:39 PM, VAXman- at SendSpamHere.ORG wrote:
>>>>>>> 10  ENQ-TYPE      PIC X(1)  VALUE EXTERNAL PQL$_ENQLM. 
>>>>>>> ..............^ %COBOL-E-EXTREFVAL, VALUE EXTERNAL clause
>>>>>>> ignored - valid only on COMP data-item
>>>>>>> 
>>>>>>> How do you put PQL$ items in to a COBOL "byte"?
>> 
>>> I have no idea what POL$_ENOLM means or what he is trying to do
>>> with it. A rough guess would be rather than declaring it external
>>> he needs to use some VMS Specific function to grab the value and
>>> load it into ENO-TYPE.
>> 
>> If SDL produces COBOL text libraries and there is a way to include
>> them (some variant of COPY?) then yes, he might be able to do the
>> equivalent of "#include <pqldef.h>" and not need the external
>> declaration.  But the external declaration is an ancient hack that
>> at one time was more reliable than depending on the existence of
>> programmer-friendly definitions, and also, if you were willing to
>> link at installation time, could insulate against version-specific
>> changes to the symbol value.
> 
> What I'm having a problem with is expecting the linker to find the 
> declared external data.  PQL_ENQLM is a SYSGEN parameter.  Not
> something the linker could find, unless linking against the system
> image, and I have no idea if linking against the system image would
> provide that parameter.
> 
> I could be wrong, hell I'm usually wrong these days.  I do not think
>  Brian gave enough information.
> 
> From my occasional playing with CREPRC what I remember is that the
> PQL parameters are used when a specific parameter is not provided.
> Thus, just don't provide that parameter to CREPRC.  I never did.
> 

I think you'll find the process defaults rarely match your needs. For me 
I create a server process username and $persona_assume before the 
$creprc but also preload the quotas from a $getuai before hand.

The linker resolved PQL$m_ENQLM symbol does NOT contain a value for lock 
limits it is merely telling creprc that the next item-list parameter 
contains this value.