Back before SYS1.LPALIB, Nucleus-resident SVC routines were named IGCxxx and
were linked into IEANUC00; transient SVC routines were named IGC00xxx with a C
zone on the last digit, resided is SYS1.SVCLIB and ran out of 1 KiB (2 KiB in
OS/VS1) SVC transient areas. The names endured, but since SVS the system just
pages in transient SVC routines. The EBCDIC code pages I've used had C) as "{".
DOS/360 had A and B transients; I don't know whether those survived to z/VSE.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
________________________________________
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Steve Thompson [ste...@wkyr.net]
Sent: Wednesday, May 31, 2023 9:32 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Q: Transient SVC ?
Sorry, but I have to ask this: What do you mean by a transient SVC?
In days gone by, I remember that SVCs had to have specific names,
so the last char of the SVC could be a "non" printable name (hazy
memories of this from having to fix/patch an SVC).
I know that DOS, DOS/V* had transients that we (DOS to MVS
migration teams), in some cases had to turn into an SVC for use
in MVS.
Just trying to remember how some of this stuff used to work/be done.
Steve Thompson
On 5/31/2023 8:42 PM, Seymour J Metz wrote:
> For transient SVC name it was a trailing C0; I was just contrasting member
> names with index levels. I guess that IBM decided to eliminate an alleged
> ambiguity between member name and relative generation.
>
>
> --
> Shmuel (Seymour J.) Metz
> http://mason.gmu.edu/~smetz3
----------------------------------------------------------------------
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
