This was close to day one on DOS/VS not MVS: CICS 1.1.??
I can not speak to the situation on MVS.? My MVS experience was a
couple decades later and my CICS work was as a systems programmer
(as we referred to the job in those days).? Not application
programmer, as I was in the 70's when my work experience was
DOS/VS.
Harold Grovesteen
On 9/11/24 17:37, Joe Monk wrote:
toggle quoted message
Show quoted text
Interesting :)
I always thought ASKTIME and EIBDATE and EIBTIME were
around since day 1.
Joe
On Wed, Sep 11, 2024 at
5:24?PM Harold Grovesteen via <h.grovsteen=
[email protected]>
wrote:
Yes,
you can just inspect low memory to locate the COMRG.
In the early days of COBOL programming in CICS/VS 1.1 on
DOS/VS, there
was a mechanism that allowed me to define a COBOL area that
had a
pointer set to 20, and lo and behold you could access the date
from the
COMRG without issuing an SVC which was not a good idea in a
CICS
application.? The date was what I needed.? But anything was
there for
the reading.
By avoiding SVC 33, CICS, the partition, did not lose control.
How COBOL implemented CICS table accesses via a COBOL defined
base-address register field was the basis for the pointer.
Just FYI from the early days.? CICS/VS with COBOL applications
provided
no mechanism for accessing the date (that I recall).? IBM
support found
my solution "interesting".
Harold Grovesteen
On 9/11/24 16:36, Paul Edwards wrote:
> On Wed, Sep 11, 2024 at 11:34 PM, Fish Fish wrote:
>
>> Each partition has its own Communications Region.
Address 20 is always set to
>> the address of the given partition's Communications
Region control block by
>> the dispatcher. It is a part of task dispatching. So
while that particular
>> partition is running, address 20 always points to its
COMRG.
> Thanks for that explanation.
>
>>> Or alternatively - use the abstraction - SVC 33
can go and
>>> inspect low memory itself?
>> That is not the purpose of SVC 33.
> Ok - I had the wrong concept there - thanks.
>
> BFN. Paul.
>
>
>
>
>
