Summary of changes

GDDM V3R2 Messages

Summary of changes

GDDM V3R2 Messages
SC33-0869-01

| Changes to this book for Version 3 Release 2

| New Information: The following are the new message identifiers for this
| major revision, including a portion of the message text and an explanation
| of when the message is issued:

| ADM0286 DATASTREAM RETRIEVAL NOT INITIALIZED

| FSGET (or FSGETE) was called without a preceding call to FSGETS. See
| topic 2.221.

| ADM0287 DATASTREAM RETRIEVAL ALREADY INITIALIZED

| FSGETS was called when datastream retrieval was already active. See
| topic 2.222.

| ADM0350 MEMBER 'a' NOT FOUND.

| Under TSO, member a of a partitioned dataset was required as input,
| but it could not be found in the dataset. See topic 2.266.

| ADM0362 DEVICE FOR FRCETYPE=DSFRCE MUST BE A PARTITIONED DATASET

| A device is to be opened with the processing option FRCETYPE=DSFRCE
| and the dataset referenced is not a partitioned dataset. See topic
| 2.270.

| ADM0642 {TYPE {1|2}} SET LOADED. CODE PAGE DIFFERS FROM APPLICATION CODE
| PAGE

| The symbol set you identified was successfully loaded from secondary
| storage but it was tagged with a code page that was different from the
| application code page. See topic 2.464.

| ADM0847 SET LOADED. CODE PAGE DIFFERS FROM APPLICATION CODE PAGE

| The symbol set you have loaded is tagged with a code page that is
| different from the application code page. See topic 2.606.

| ADM0881 DEVICE CODE PAGE n1 WITH CHARACTER SET n2 IS UNSUPPORTED

| The processing option DEVCPG or the device code page returned by the
| device query (if DEVCPG not present) value n1 and processing option
| DEVCSET value n2 is an unsupported combination as there is no matching
| entry in the GDDM translate table module ADMDATRN. See topic 2.630.

| ADM0882 FRCETYPE=DSFRCE NOT ALLOWED FOR DOCUMENTS

| A device is to be opened with the processing options FRCETYPE=DSFRCE
| and OFDSTYPE=DOC. See topic 2.631.

| ADM2050 DATA SET NAME IS LONGER THAN 44 CHARACTERS

| The GDDM Print Queue data set name entered in the Setup Option was
| longer than 44 characters. See topic 2.920.

| ADM2051 UNIT TYPE MUST BE SPECIFIED WHEN VOLUME SERIAL IS SPECIFIED

| A Unit type is required if a Volume Serial is entered in the Setup
| Option panel. See topic 2.921.

| ADM2052 GDDM PRINT QUEUE DATA SET NOT FOUND; CHECK SETUP OPTION

| The name of the GDDM Print Queue that is to be managed by the PQM must
| first be entered through the Setup panel. See topic 2.922.

| ADM2053 VOLUME SPECIFIED FOR GDDM PRINT QUEUE DATA SET IS NOT MOUNTED

| The specified volume or an acceptable volume was not mounted and the
| user did not have volume mounting authorization through the DYNALLOC
| request. See topic 2.923.

| ADM2054 VOLUME SPECIFIED FOR GDDM PRINT QUEUE DATA SET IS NOT AVAILABLE

| The Volume specified for the GDDM Print Queue data set on the Setup
| option panel was not available for the DYNALLOC request. See topic
| 2.924.

| ADM2055 UNIT TYPE SPECIFIED FOR GDDM PRINT QUEUE DATA SET IS NOT VALID

| The Unit type specified for the GDDM Print Queue data set on the Setup
| Option panel was not valid for the DYNALLOC request. See topic 2.925.

| ADM2056 UNIT TYPE SPECIFIED FOR GDDM PRINT QUEUE DATA SET IS NOT VALID

| The DYNALLOC request for the GDDM Print Queue could not complete
| because the specified GDDM Print Queue was in use by another
| application. See topic 2.926.

| ADM2057 DYNAMIC ALLOCATION FAILED FOR THE GDDM PRINT QUEUE, RC=X''&RCODE''

| The DYNALLOC request for the GDDM Print Queue failed with the
| specified return code. See topic 2.927.

| ADM2058 ERROR OPENING GDDM PRINT QUEUE DATA SET

| Execution of the OPEN macro for the specified GDDM Print Queue data
| set has failed. See topic 2.928.

| ADM2059 PRINTER HAS BEEN DELETED FROM PRINT QUEUE DATA SET

| The entry in the GDDM Print Queue for the specified printer has been
| deleted, together with any associated print requests. See topic
| 2.929.

| ADM2060 'a1' 'a2' DELETED

| The print request a2 for printer a1 has been deleted from the GDDM
| Print Queue through the Print Queue Manager. See topic 2.930.

| ADM2061 PRINTER NAME NOT FOUND IN PRINT QUEUE DATA SET

| The printer specified on a delete or list panel of the PQM could not
| be found in the GDDM Print Queue. See topic 2.931.

| ADM2062 NO SPACE AVAILABLE IN QAB FOR ADDITIONAL PRINTER

| To add a printer dynamically to the GDDM Print Queue through the PQM,
| spare 'slots' are required in the QAB records of the Print Queue. See
| topic 2.932.

| ADM2063 PRINTER NAME ALREADY DEFINED IN PRINT QUEUE DATA SET

| The printer name specified on the Add Printer panel of the Print Queue
| Manager (PQM) already exists in the GDDM Print Queue. See topic
| 2.933.

| ADM2064 PRINTER ADDED TO PRINT QUEUE DATA SET

| An entry for the printer has been created in the QAB record of the
| GDDM Print Queue. See topic 2.934.

| ADM2065 RESPOND WITH "YES" or "NO"

| If a printer that is requested to be deleted has print requests queued
| for it, confirmation is required for the deletion. See topic 2.935.

| ADM2066 NO PRINTERS HAVE BEEN DEFINED TO GDDM PRINT QUEUE

| The List All Printers panel was chosen and no printers were found on
| the GDDM Print Queue. See topic 2.936.

| ADM2067 NO REQUESTS QUEUED TO THIS PRINTER

| The option to reroute (*) all requests was chosen on the Reroute
| panel. See topic 2.937.

| ADM2068 REQUEST(S) REROUTED TO DESTINATION PRINTER

| The option to reroute (*) all requests was chosen on the Reroute
| panel. See topic 2.938.

| ADM2069 ONLY SELECTED REQUESTS CAN BE REROUTED TO THE SAME PRINTER

| The same printer was chosen for the origination printer and
| destination printer on the Reroute panel and then the option to
| reroute all requests (*) was selected. See topic 2.939.

| ADM2070 DESTINATION PRINTER NOT DEFINED TO GDDM PRINT QUEUE

| The printer specified as the destination printer on the Reroute panel
| could not be found in the GDDM Print Queue. See topic 2.940.

| ADM2071 ORIGINATION PRINTER NOT DEFINED TO GDDM PRINT QUEUE

| The printer specified as the origination printer on the Reroute
| Requests panel could not be found in the GDDM Print Queue. See topic
| 2.941.

| ADM2072 THE REQUEST IS CURRENTLY BEING PRINTED

| A print request was selected to be deleted or rerouted to another
| printer and the request was already allocated to the TSO Print Utility
| for printing. See topic 2.942.

| ADM2073 'a1' PRINTER IS NOW SET TO 'HOLD' STATUS, "N" TO RELEASE

| Printer a1 has been set to 'HOLD' status. See topic 2.943.

| ADM2074 'a1' IS NOW RELEASED FROM 'HOLD' STATUS

| Printer a1 has been released from 'HOLD' status. See topic 2.944.

| ADM2075 YOU HAVE NOT BEEN AUTHORIZED TO USE THE GDDM PRINT QUEUE MANAGER

| The user has not been authorized to use the Print Queue Manager. See
| topic 2.945.

| ADM2076 REQUEST ALREADY PROCESSED BY ANOTHER USER

| Another user of the Print Queue Manager has processed this request and
| it was no longer on the queue for this printer. See topic 2.946.

| ADM3161 DBCS FONTS ARE NOT SUPPORTED FOR THIS DEVICE

| The composite document being processed contains text that requires a
| DBCS font, but GDDM does not support use of DBCS fonts on the current
| device. See topic 2.1117.

| Changed Information: The following are the changed message identifiers
| for this major revision, including a portion the message text and an
| explanation of the change made to the message:

| 3.1 ADM0277 '{FSSAVE|FSSHOW|FSSHOR|FSCOPY|GSCOPY|DSCOPY|MAPPING}' IS NOT
| SUPPORTED FOR THIS DEVICE

| 3.2 ADM0277 '{FSSAVE|FSSHOW|FSSHOR|FSCOPY|GSCOPY|DSCOPY|MAPPING|
| DSFRCE|FSFRCE}' IS NOT SUPPORTED FOR THIS DEVICE

| Changed message, see topic 2.215.

| The message text and explanation have changed.

| ADM0328 'a1' ERROR CODE n-X'xx' ON 'a2'

| Changed message, see topic 2.249.

| The explanation and programmer response have changed.

| ADM0446 RETURN CODE n FROM EXEC 'ADMQPOST'

| Changed message, see topic 2.317.

| The explanation has changed.

| ADM3294 CGM ERROR CODE abbcc AT LINE n1 OFFSET n2

| Changed message, see topic 2.1233.

| The explanation has changed.

Changes to this book for Version 3 Release 1

Various editorial changes have been made throughout this book to improve the clarity of the text.

Each prefix group of messages is now presented in a separate topic.

Messages issued by the GDDM-PCLK feature (GQD-prefix messages) are now included.

Messages issued by the GDDM Central Slide and Plot Facility (GDDM-CSPF) are no longer included, because GDDM-CSPF is not available for use with GDDM Version 3 Release 1.

Notices | Terms of use | Support | Contact z/OS