MVS Programming: Authorized Assembler Services Reference .

About this documentThis document supports z/OS (5694-A01) and z/OS.e (5655-G52). This document describes the authorized services that the MVS operating systemprovides; that is, services available only to authorized programs. An authorizedprogram must meet one or more of the following requirements:v Running in supervisor statev Running under PSW key 0-7v Running with APF-authorization.Some of the services included in this document are not authorized, but are includedbecause they are of greater interest to the system programmer than to the generalapplications programmer. The functions of these services are of such a nature thattheir use should be limited to programmers who write authorized programs.Services are also included if they have one or more authorized parameters —parameters available only to authorized programs.Programmers using assembler language can use the macros described in thisdocument to invoke the system services that they need. This document includes thedetailed information — such as the function, syntax, and parameters — needed tocode the macros.This document is divided into four volumes. Volumes 1 through 4 present the macrodescriptions in alphabetical order.Who should use this document This document is for the programmer who is using assembler language to code asystem program. A system program is usually one that runs in supervisor state orruns with PSW key 0-7 or runs with APF authorization.The document assumes a knowledge of the computer, as described in Principles ofOperation, as well as an in-depth knowledge of assembler language programming.System macros require High Level Assembler. Assembler language programming isdescribed in the following books:v HLASM Programmer’s Guidev HLASM Language ReferenceUsing this book also requires you to be familiar with the operating system and theservices that programs running under it can invoke.How to use this documentThis document is one of the set of programming documents for MVS. This setdescribes how to write programs in assembler language or high-level languages,such as C, FORTRAN, and COBOL. For more information about the content of thisset of documents, see z/OS Information Roadmap. Copyright IBM Corp. 1988, 2003ix

Where to find more informationWhere necessary, this document references information in other documents, usingshortened versions of the document title. For complete titles and order numbers ofthe documents for all products that are part of z/OS. see z/OS InformationRoadmap (GC28-1727).The following table lists titles and order numbers for documents related to otherproducts.Short Title Used in ThisDocumentTitlePrinciples of Operation*z/ArchitectureOrderNumberPrinciples of OperationSA22-7832* Use the appropriate Principles of Operation document for the hardware you have installed.PSF/MVS SystemProgramming GuidePrint Services Facility/MVS SystemProgramming GuideS544-3672Accessing z/OS licensed documents on the Internetz/OS licensed documentation is available on the Internet in PDF format at the IBMResource Link Web site at:http://www.ibm.com/servers/resourcelinkLicensed documents are available only to customers with a z/OS license. Access tothese documents requires an IBM Resource Link user ID and password, and a keycode. With your z/OS order you received a Memo to Licensees, (GI10-0671), thatincludes this key code. 1To obtain your IBM Resource Link user ID and password, log on to:http://www.ibm.com/servers/resourcelinkTo register for access to the z/OS licensed documents:1. Sign in to Resource Link using your Resource Link user ID and password.2. Select User Profiles located on the left-hand navigation bar.Note: You cannot access the z/OS licensed documents unless you have registeredfor access to them and received an e-mail confirmation informing you thatyour request has been processed.Printed licensed documents are not available from IBM.To print licensed documents, you can use the PDF format on either z/OS LicensedProduct Library CD-ROM or IBM Resource Link .Using LookAt to look up message explanationsLookAt is an online facility that lets you look up explanations for most messagesyou encounter, as well as for some system abends and codes. Using LookAt to findinformation is faster than a conventional search because in most cases LookAtgoes directly to the message explanation.1. z/OS.e customers received a Memo to Licensees, (GI10-0684) that includes this key code.xz/OS V1R4.0 MVS Auth Assm Services Reference LLA-SDU

You can access LookAt from the Internet ookat/ or from anywhere in z/OS orz/OS.e where you can access a TSO/E command line (for example, TSO/E prompt,ISPF, z/OS UNIX System Services running OMVS).The LookAt Web site also features a mobile edition of LookAt for devices such asPocket PCs, Palm OS, or Linux-based handhelds. So, if you have a handhelddevice with wireless access and an Internet browser, you can now access LookAtmessage information from almost anywhere.To use LookAt as a TSO/E command, you must have LookAt installed on your hostsystem. You can obtain the LookAt code for TSO/E from a disk on your z/OSCollection (SK3T-4269) or from the LookAt Web site’s Download link.Information updates on the webFor the latest information updates that have been provided in PTF cover letters andDocumentation APARs for z/OS and z/OS.e, see the online document cmd/BOOKS/ZIDOCMST/CCONTENTSThis document is updated weekly and lists documentation changes before they areincorporated into z/OS publications.About this documentxi

xiiz/OS V1R4.0 MVS Auth Assm Services Reference LLA-SDU

Summary of changesSummary of changesfor SA22-7611-04z/OS Version 1 Release 4as updated December 2003The document contains information previously presented in z/OS MVSProgramming: Authorized Assembler Services Guide, SA22-7611-03, whichsupports z/OS Version 1 Release 4.This document includes information in support of the Consoles Enhancements, anunpriced feature, which will be generally available in 1Q2004.This document contains terminology, maintenance, and editorial changes. Technicalchanges or additions to the text and illustrations are indicated by a vertical line tothe left of the change.Starting with z/OS V1R2, you may notice changes in the style and structure ofsome content in this document—for example, headings that use uppercase for thefirst letter of initial words only, and procedures that have a different look and format.The changes are ongoing improvements to the consistency and retrievability ofinformation in our documents.Summary of changesfor SA22-7611-03z/OS Version 1 Release 4The document contains information previously presented in z/OS MVSProgramming: Authorized Assembler Services Reference LLA-SDU, SA22-7611-02,which supports z/OS Version 1 Release 3.New informationv Information is added to indicate this books supports z/OS.e.This document contains terminology, maintenance, and editorial changes, includingchanges to improve consistency and retrievability.Summary of changesfor SA22-7611-02z/OS Version 1 Release 3The document contains information previously presented in z/OS MVSProgramming: Authorized Assembler Services Reference LLA-SDU, SA22-7611-01,which supports z/OS Version 1 Release 2.New informationv An appendix with z/OS product accessibility information has been added.This document contains terminology, maintenance, and editorial changes, includingchanges to improve consistency and retrievability. Copyright IBM Corp. 1988, 2003xiii

Summary of changesfor SA22-7611-01z/OS Version 1 Release 2The document contains information previously presented in z/OS MVSProgramming: Authorized Assembler Services Reference LLA-SDU, SA22-7611-00,which supports z/OS Version 1 Release 1.Changed informationv “Using the Services” on page 1 has been changed to reflect 64–bit VirtualStorage addressing.v SDUMPX — Dump Virtual Storage macro has been changed to includeexpanded functions available when using 64–bit address mode.v LOAD — Bring a Load Module Into Virtual Storage is changed to provide supportfor APAR OW18167 by including reference to new parameters on theCSVQUERY macro.This document contains terminology, maintenance, and editorial changes, includingchanges to improve consistency and retrievability.Summary of changesfor SA22-7611-00z/OS Version 1 Release 1The document contains information also presented in MVS/ESA Programming:Authorized Assembler Services Reference, Volume 3 (LLACOPY-SDUMPX).xivz/OS V1R4.0 MVS Auth Assm Services Reference LLA-SDU

Using the ServicesMacros and callable services are programming interfaces that application programscan use to access MVS system services. This chapter provides general informationand guidelines about how to use the macros and callable services accurately andefficiently. For more specific and detailed information about coding a particularmacro or callable service, see the individual service description in this book.Some of the topics covered in this chapter apply only to macros, some apply only tocallable services, and some apply to both. This chapter uses the word ″services″when referring to information that applies to both service types. When informationapplies only to one type or the other, the particular service type is specified.The following table lists the topics covered in this chapter and whether the topicapplies to macros, callable services, or both:Topic“Compatibility of MVS Macros”“Addressing Mode (AMODE)” on page 2“Address Space Control (ASC) Mode” on page 3“ALET Qualification” on page 3“User Parameters” on page 4“Telling the System about the Execution Environment” on page 5“Specifying a Macro Version Number” on page 6“Register Use” on page 7“Handling Return Codes and Reason Codes” on page 8“Handling Program Errors” on page 9“Handling Environmental and System Errors” on page 9“Using X-Macros” on page 10“Macro Forms” on page 11“Coding the Macros” on page 12“Coding the Callable Services” on page 15“Including Equate (EQU) Statements” on page 16“Link-Editing Linkage-Assist Routines” on page 16“Service Summary” on page 16Service thBothMacrosMacrosMacrosCallable ServicesCallable ServicesCallable ServicesBothCompatibility of MVS MacrosWhen IBM introduces a new version or a new release of an existing version, thenew version or release supports all MVS macros from previous versions andreleases. Programs assembled on an earlier level of MVS that issue macros will runon later levels of MVS.In most cases, the reverse is also true. When you assemble programs that issuemacros on a particular version and release of MVS, those programs can run onearlier versions and releases of MVS, provided you request only those functionsthat are supported by the earlier version and release. This is useful for installationsthat write applications that might be assembled on one level of MVS, but run on adifferent level.As MVS supports new architectures, addressability changes; for example, supportfor access registers was introduced in MVS/ESA. Support for 64-bit registers wasintroduced in OS/390 R10. To take best advantage of the new architectures, somemacros have more than one possible expansion. You are required to have the Copyright IBM Corp. 1988, 20031

macro expand according to the environment in which the program runs. This topicis described in this introductory information.The problem of compatibility is not the same as selecting a macro version via thePLISTVER parameter to ensure the correct parameter list size for a macro. Forselecting a parameter list version number, see “Specifying a Macro VersionNumber” on page 6.Addressing Mode (AMODE)A program can run in 24-bit, 31-bit, or 64-bit addressing mode. A program thatexecutes in 24-bit or 31-bit addressing mode can invoke most of the servicesdescribed in this book. A program that executes in 64-bit addressing mode has asmaller group of services that it can invoke.In general,v A program running in 24-bit addressing mode cannot pass parameters orparameter addresses that are higher than 16 megabytes. However, there areexceptions. For example, a program running in 24-bit addressing mode can:– Free storage above 16 megabytes using the FREEMAIN macro– Allocate storage above 16 megabytes using the GETMAIN macro– Use cell pool services for cell pools located in storage above 16 megabytesusing the CPOOL macro– Use page services for storage locations above 16 megabytes using thePGSER macro.v A program running in 24-bit or 31-bit addressing mode cannot pass parameteraddresses that are higher than 2 gigabytes, unless stated otherwise in theindividual service description.v If a program running in 31-bit or 64-bit addressing mode issues a service,parameters and parameter addresses can be above or below 16 megabytes,unless otherwise stated in the individual service description.Some macros can generate code that is appropriate for programs in either 64–bitaddressing mode or 24–bit or 31–bit addressing mode. These macros check aglobal symbol set by the SYSSTATE macro. See “Telling the System about theExecution Environment” on page 5 for more information.When you call a callable service in 24-bit or 31-bit addressing mode, you must pass31-bit addresses to the system service regardless of what addressing mode yourprogram is running in. If your program is running in 24-bit mode and you use acallable service, you must set the high-order byte of parameter addresses to zeros.You can invoke the following services in 64-bit addressing mode, subject to the“SVC or PC” restrictions mentioned below, but you may not pass parameters andparameter addresses above 2 gigabytes: ABEND, ATTACHX, CALLDISP, CHAP,CSVQUERY, DELETE, DEQ, DETACH, DOM, DSPSERV, DYNALLOC, ENQ,ESPIE, ESTAEX, EXCP, FREEMAIN, GETMAIN, IDENTIFY, GTRACE, IARVSERV,LINKX, LOAD, MODESET, PHSER, POST, RESERVE, SDUMPX, SETRP, STAX,STIMER, STIMERM, STORAGE, SYNCHX, TIME, TIMEUSED, TTIMER, VRADATA,WAIT, WTO, WTOR, and XCTL.You can invoke the following service in 64-bit addressing mode and may passparameters and parameter addresses above 2 gigabytes: IARV64.2z/OS V1R4.0 MVS Auth Assm Services Reference LLA-SDU

Before invoking a service in 64-bit addressing mode, you must inform systemmacros, by specifying SYSSTATE AMODE 64, that you are in 64-bit addressingmode. Only those options that result in calling the system by an SVC or PC may beinvoked in 64-bit addressing mode. Any option that results in calling the system bya branch-entry may not be invoked in 64-bit addressing mode.Unless explicitly stated otherwise, you should assume that a given service may notbe invoked in 64-bit addressing mode and cannot accept parameters and parameteraddresses above 2 gigabytes.For information about 64-bit addressing mode and the 64-bit GPR, see z/OS MVSProgramming: Extended Addressability Guide.Address Space Control (ASC) ModeA program can run in either primary ASC mode or access register (AR) ASC mode.In primary mode, the processor uses the contents of general purpose registers(GPRs) to resolve an address to a specific location. In AR mode, the processoruses the contents of ARs as well as the contents of GPRs to resolve an address toa specific location. See z/OS MVS Programming: Assembler Services Guideformore detailed information about AR mode.Some macros can generate code that is appropriate for programs in either primarymode or AR mode. These macros check a global symbol set by the SYSSTATEmacro. See “Telling the System about the Execution Environment” on page 5 formore information. Table 3 on page 17 lists the macros that check the global symbol.Some services can generate code that is appropriate for programs in primary modeonly. If you write a program in AR mode that invokes one or more services, checkthe description in this book for each service your program issues. Unless thedescription indicates that a service supports callers in AR mode, the service doesnot support callers in AR mode. In this case, use the SAC instruction to change theASC mode of your program and issue the service in primary mode.Whether the caller is in primary or AR ASC mode, the system uses ARs 0-1 and14-15 as work registers across any service call.ALET QualificationThe address space where you can place parameters varies with the individualservice:v All services allow you to place parameters in the primary address space.v Some services require you to place parameters in the primary address space.v Some services allow you to place parameters in any address space.To identify where a service allows parameters to be located, read the individualservice description.Programs in AR mode that pass parameters must use an access register and thecorresponding general purpose register together (for example, access register 1and general purpose register 1) to identify where the parameters are located. Theaccess register must contain an access list entry token (ALET) that identifies theaddress space where the parameters reside. The general purpose register mustidentify where, within the address space, the parameters reside.The only ALETs that MVS services typically accept are:Using the Services3

v Zero (0), which specifies that the parameters reside in the caller’s primaryaddress spacev An ALET for a public entry on the caller’s dispatchable unit access list (DU-AL).v An ALET for a common area data space (CADS)MVS services do not accept the following ALETs, and you must not attempt to passthem to a service:v One (1), which signifies that the parameters reside in the caller’s secondaryaddress spacev An ALET that is on the caller’s primary address space access list (PASN-AL) thatdoes not represent a CADSv An ALET for a private entry on the PASN-AL or the DU-AL.Throughout, this book uses the term AR/GPR n to mean an access register and itscorresponding general purpose register. For example, to identify access register 1and general purpose register 1, this book uses AR/GPR 1.User ParametersSome macros that you can issue in AR mode include control parameters, userparameters, or both. Control parameters refer to the macro parameter list, and tothe parameters whose addresses are in the parameter list. Control parameterscontrol the operation of the macro itself. User parameters are parameters that theuser provides to be passed through to a user routine. For example, the PARAMparameter on the ATTACHX macro defines user parameters. The ATTACHX macropasses these parameters to the routine that it attaches. All other parameters on theATTACHX macro are control parameters that control the operation of the ATTACHXmacro.Notes:1. User parameters are sometimes referred to as problem program parameters.2. Control parameters are sometimes referred to as system parameters or controlprogram parameters.The macros shown in Table 1 allow a caller in AR mode to pass information in theform of a parameter list (or parameter lists) to another routine. This table identifiesthe parameter that receives the ALET-qualified address of the parameter list andtells you where the target routine finds the ALET-qualified address.Table 1. Passing User Parameters in AR ModeMacroParameterLocation of User Parameter List AddressATTACH/ATTACHXPARAM,VL 1AR/GPR 1 contains the address of a list ofaddresses and ALETs. (See Figure 1 for

Operation, as well as an in-depth knowledge of assembler language programming. System macros require High Level Assembler. Assembler language programming is described in the following books: v HLASM Programmer’s Guide v HLASM Language Reference Using this book also requires you to be familiar with the operating system and the