I fear that the OP is misunderstanding both what "SVC calling" in general and "SYNCH" in particular mean.
SYNCH does not fetch a module. You can only SYNCH to a module that is already fetched. So that leaves you with having to have started with fetching the mode. And in general you would not use SYNCH unless you are trying to run the target with less authority than the issuer of SYNCH has. There really is no such thing as "SVC calling". There is LINK or LINKX, ATTACH or ATTACHX, XCTL or XCTLX, and then there is LOAD and then CALL. A module that is the by-product of the binder is a module is a module. It is not different per language. It might have characteristics unique to its source language. And of course something that creates an executable "on the fly", as Java can do, does not go through module fetch. If you have a load module (in a PDS) or a program object (in a PDSE), you can LINK to it. LINK happens to be an SVC but that is not something you (the user) cares about. It could have been a stacking PC if the architecture evolved from a different starting point. Your program invokes LINK, LINK processing fetches the module, LINK processing sets things up so that the target module gets control, whether it is assembler, C, PL/I, COBOL, you name it. Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
