> A type 1 or type 6 SVC can issue SUSPEND, but noting that, in doing so,
> this is basically ending the SVC's processing.
Not quite; typically the routine will at least schedule an SRB after the
SUSPEND and before exiting.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
"As I understand it... a type 1 or 6 SVC cannot SUSPEND, WAIT, or PAUSE
synchronously at all. If they need to finish something later, they
schedule it and quit."
Not true. See note 8 in the link below...
https://www.ibm.com/docs/en/zos/2.1.0?topic=routines-programming-conventions-svc
As
I'd already seen it. It does not contradict my statement at all. Shmuel
also mentioned this in passing.
sas
On Fri, Nov 26, 2021 at 12:04 PM Joe Monk wrote:
> "As I understand it... a type 1 or 6 SVC cannot SUSPEND, WAIT, or PAUSE
> synchronously at all. If they need to finish something
"As I understand it... a type 1 or 6 SVC cannot SUSPEND, WAIT, or PAUSE
synchronously at all. If they need to finish something later, they
schedule it and quit."
Not true. See note 8 in the link below...
https://www.ibm.com/docs/en/zos/2.1.0?topic=routines-programming-conventions-svc
Joe
On
As I understand it... a type 1 or 6 SVC cannot SUSPEND, WAIT, or PAUSE
synchronously at all. If they need to finish something later, they
schedule it and quit.
The differences between type 1 and 6 (and the others) are discussed in the
MVS Auth Service Guide.
sas
On Fri, Nov 26, 2021 at 9:23 AM
The devil is in the details. There is a discussion in authorized services.
Briefly, for a type 1 SVC, you suspend the current RB, schedule an SRB or
whatever, and ultimately exit normally. When you exit, the suspension takes
effect.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
Thanks, Seymour, for the info about type-6s.
WRT GUPI, like most other ISVs, I use them when I can, and accept the
occasional recoding obligations when I can't.
My real question is... What happens when a type-1 SVC SUSPENDs? (Or
for that matter, when any other locked or disabled environment
