PSF for z/OS: Messages and Codes
PSF for z/OS: Messages and Codes
Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
APS600 to APS699 PSF for z/OS: Messages and Codes G550-0432-04 |
|
APS600 to APS699APS600I USER IS NOT AUTHORIZED TO OVERRIDE DEFAULT VALUE. Explanation:
This message is issued when DPAGELBL or SYSAREA parameter is equal to YES on the PRINTDEV statement, and the user specifies NO without correct Resource Access Control Facility (RACF®) authorization. System action:
PSF releases the current data set back to JES and requests that it be held by the system. User response:
Ask the system security administrator for permission to override the default values, or change the output so that it does not override the default. System programmer response:
Determine whether the user should be authorized to override SYSAREA or DPAGELBL. If the user should be authorized, use RACF to give the user the appropriate authorization. For information on how to do this, see the RACF publications for your operating system. Operator response:
Notify the security administrator of this error. For a command to release the data set for printing after the problem has been corrected, see the publication containing JES operator commands for your operating system. Problem determination:
Items 2, 9, 11. APS601I USERLIB SPECIFICATION IS IGNORED. Explanation:
JES did not provide PSF the UTOKEN parameter required to perform a RACF authorization check for a user library (USERLIB). This condition can arise if the correct prerequisite level of z/OS®, RACF, or JES is not installed, or if any of those programs contains a logic error. System action:
Processing of the data set continues by using system libraries only. User response:
Inform your system programmer that this error occurred. System programmer response:
Ensure that the correct levels of z/OS, RACF, and JES for this version of PSF are installed. If the correct levels are installed, follow the procedures described in PSF for z/OS: Diagnosis before contacting the IBM® Support Center. Operator response:
Inform your system programmer that this error occurred. Problem determination:
Items 1, 17, 27. APS602I PSF FAILED TO FIND CNTL STATEMENT control statement IN
CURRENT STEP, REASON CODE = reason code. Explanation:
PSF started the Scheduler JCL Facility (SJF) to find the scheduler work block for the control statement in the current step specified by the CNTL keyword on the DD statement. The SJF FIND macro failed and returned the reason code identified in this message. The values of the reason codes and their meanings are:
System action:
PSF fails to initialize. User response:
No response is necessary. System programmer response:
This error was probably caused by an error in specifying the JCL statements for the startup procedure. For information about specifying JCL statements, see PSF for z/OS: Customization. Correct the error and restart the procedure. If you have made any changes to the startup procedure, be sure to CANCEL the STARTED TASK before trying again. Operator response:
Inform your system programmer that this error occurred. Problem determination:
Items 2, 17, 27. APS603I PRINTDEV VERB NOT FOUND WITHIN CNTL GROUP control group. Explanation:
PSF started the Scheduler JCL Facility (SJF) to find the scheduler work block chain for a PRINTDEV verb in the control group identified in this message. The PRINTDEV verb was not found. System action:
PSF fails to initialize. User response:
No response is necessary. System programmer response:
Omission of the PRINTDEV JCL statements in the PSF startup procedure probably caused this error. For information about specifying JCL statements for the PSF startup procedure, see PSF for z/OS: Customization. Correct the error and restart the procedure. Operator response:
Inform your system programmer that this error occurred. Problem determination:
Items 2, 17, 27. APS604I ONE OR MORE KEYWORDS REQUIRED TO INITIALIZE AN SNA DEVICE WAS
NOT SPECIFIED ON THE PRINTDEV STATEMENT. ALL REQUIRED KEYWORDS MUST
BE SPECIFIED BEFORE THE PROCEDURE CAN BE STARTED. Explanation:
To start an SNA-attached printer, all required keywords must be specified. System action:
PSF fails to initialize. User response:
No response is necessary. System programmer response:
Ensure that all required keywords for the SNA-attached printer are specified in the PRINTDEV JCL statement in the PSF startup procedure. For more information, see PSF for z/OS: Customization. The required SNA-attached keywords are:
Operator response:
Inform your system programmer that this error occurred. Problem determination:
Items 1, 17, 24, 26. APS605I VIRTUAL STORAGE COULD NOT BE ACQUIRED FOR TRACING. {ALL |
EXTERNAL} TRACING FOR {prtname | fssname} HAS BEEN
CANCELED. Explanation:
Virtual storage could not be acquired for all the required trace control blocks. The indicated trace types have been canceled. System action:
The indicated types of tracing were canceled. User response:
No response is necessary. System programmer response:
Increase the REGION size specified in the PSF startup procedure. Operator response:
Inform your system programmer that this error occurred. Problem determination:
Items 1, 8, 17. APS606I PERMANENT I/O ERROR OCCURRED ON TRACE DATA SET, unit
name, ddname, device type, command, error. Explanation:
The PSF SYNAD routine encountered a permanent I/O error on the trace data set. System action:
Tracing stops. User response:
Inform your system programmer that this error occurred. System programmer response:
Correct the error on the basis of the information provided by the message. Operator response:
Inform your system programmer that this error occurred. Problem determination:
Item 1, 2, 8, 17, 18, 19. APS607I COMMAND (command) NOT PROCESSED -
FSA (fsa name) IS NOT INITIALIZED. Explanation:
The fsa name specified in a command was not initialized. System action:
AFP Download Plus continues processing. User response:
No response is necessary. System programmer response:
No response is necessary. Operator response:
Enter the command again after the specified FSA has been initialized by AFP Download Plus. Problem determination:
Item 1, 17, 27. APS608I PSF GTF TRACING HAS BEEN {ACTIVATED | DEACTIVATED}. Explanation:
PSF has activated or deactivated tracing to Generalized Trace Facility (GTF). When activated, PSF Generalized Trace Facility issues the GTRACE macro request to have trace data written to the GTF data set. When deactivated, PSF stops writing trace data to GTF. System action:
PSF continues processing the data. User response:
No response is necessary. System programmer response:
No response is necessary. Operator response:
No response is necessary. Problem determination:
Items 1, 17, 27. APS609I MUTUALLY EXCLUSIVE KEYWORDS WERE SPECIFIED. SNA-REQUIRED
KEYWORDS APPLID OR LUNAME WERE SPECIFIED WITH TCP/IP-REQUIRED KEYWORD
IPADDR. Explanation:
To start the printer, conflicting protocol keywords must be removed from the Printer Inventory or a PRINTDEV JCL statement in the PSF startup procedure. System action:
PSF fails to initialize. User response:
No response is necessary. System programmer response:
Remove the keywords from the Printer Inventory or the PRINTDEV JCL statement for the protocol not used to communicate with the device. For more information on how to specify Printer Inventory options or a PRINTDEV statement, see PSF for z/OS: Customization. The keywords required for an SNA-attached printer are:
The keyword required for a TCP/IP-attached printer is:
Operator response:
Inform your system programmer that this error occurred. Problem determination:
Items 1, 17, 24, 16. APS610I GTF RETURN CODE = rc: error text. Explanation:
Generalized Trace Facility (GTF) has returned a nonzero return code from the GTRACE request. The return code rc and the error text explain the error. The return codes and error text are:
PSF issues this message when attempting to start a PSF trace and direct its output to the GTF trace data set. If the message is received, GTF might not have been started with the correct USR event IDs. If you use the command to start PSF tracing, you must specify USR=(FD0,FD4). If you do not want both types of event, start GTF with the appropriate event ID. Then, if you want FD0, add EID=PSF to the MODIFY command; or, if you want only FD4 entries, add EID=FSI to the MODIFY command. System action:
The action depends on the return code; PSF might or might not continue tracing. For return codes 18 and 20, GTF tracing continues. For the other return codes listed, GTF tracing stops. For unknown return codes, GTF tracing stops. User response:
No response is necessary. System programmer response:
For more information on the return codes, see z/OS MVS Diagnosis: Tools and Service Aids or z/OS MVS Diagnosis: Reference. Operator response:
Inform your system programmer that this error occurred. Problem determination:
Items 1, 17, 27. APS611I COMMAND (TRACEOFF) NOT PROCESSED — TRACING IS NOT ACTIVE. Explanation:
The TRACEOFF command was not processed because tracing was not active. System action:
PSF continues processing. User response:
No response is necessary. System programmer response:
No response is necessary. Operator response:
No response is necessary. Problem determination:
Items 1, 17, 27. APS612I COMMAND (command) NOT PROCESSED —
NO TRACE DATA SET ALLOCATED FOR (printer-name | notify
task). Explanation:
A trace request was received for a printer or notify task, but no trace data set was allocated for that printer or notify task. System action:
The entire command is ignored and processing continues with the next command entered. User response:
No response is necessary. System programmer response:
If using the Printer Inventory, identify the trace data set by using the FSA-trace-dsname parameter or the NST-trace-dsname parameter. Otherwise, identify the trace data set with a DD statement in the startup procedure. Operator response:
Ask your system programmer to identify the required trace data set, or start tracing with the GTF format. Problem determination:
Items 1, 17, 27. APS613I COMMAND (command) NOT PROCESSED — PRINTER
(printer-name) IS NOT ACTIVE. Explanation:
The printer-name specified in a command was not active. System action:
PSF continues processing. User response:
No response is necessary. System programmer response:
No response is necessary. Operator response:
Enter the command again after starting the named printer. Problem determination:
Items 1, 17, 27. APS614I THE VALUE SPECIFIED FOR THE keyword KEYWORD ON THE
OUTPUT STATEMENT IS NOT VALID. Explanation:
The value given for the indicated keyword contained embedded blanks or too many decimal digits, or it specified an unrecognized unit. System action:
The data set is not printed. User response:
Correct the specification for the keyword and resubmit the job. System programmer response:
If the error is on an OUTPUT statement for a separator page or the message data set, correct the specification for the keyword in the PSF startup procedure and restart the FSA. Operator response:
No response is necessary. Problem determination:
Items 2, 3. APS615I RESPTIME OR NORESP KEYWORD SPECIFIED WITHOUT THE OTHER ON
THE prtnnnn PRINTDEV STATEMENT. Explanation:
The NORESP keyword defines the action to be taken when the time specified by the RESPTIME keyword expires. If one of these keywords is specified, both must be given. Only one of them was specified. System action:
FSA startup for PRINTER prtnnnn is canceled. User response:
No response is necessary. System programmer response:
Correct the PRINTDEV statement for prtnnnn. Operator response:
Inform your system programmer that this error occurred. Problem determination:
Items 1, 17, 24. APS616I THE NORESP KEYWORD ON THE prtnnnn PRINTDEV STATEMENT
CONTAINS AN INCORRECT ACTION PARAMETER. Explanation:
The NORESP keyword was specified on the PRINTDEV statement for printer prtnnnn with an incorrect action type. System action:
FSA startup for printer prtnnnn is canceled. User response:
No response is necessary. System programmer response:
Correct the PRINTDEV statement for printer prtnnnn. Operator response:
Inform your system programmer that this error occurred. Problem determination:
Items 1, 17, 24. APS617I THE FORMAT OF THE NOTIFY OPTION OF THE NORESP KEYWORD IS
NOT VALID ON THE prtnnnn PRINTDEV STATEMENT. Explanation:
NORESP=NOTIFY was specified on the PRINTDEV statement for printer prtnnnn, but the format of the NOTIFY option was incorrect. System action:
FSA startup for printer prtnnnn is canceled. User response:
No response is necessary. System programmer response:
Correct the PRINTDEV statement for prtnnnn. Operator response:
Inform your system programmer that this error occurred. Problem determination:
Items 1, 17, 24. APS618I RESPONSE TIMEOUT OR NO RESPONSE ACTION SPECIFIED WITHOUT
THE OTHER IN THE PRINTER INVENTORY FOR fsa_name. Explanation:
The no response action parameter defines the action to be taken when the time specified by the response timeout parameter expires. If one of these parameters is specified, both must be given. Only one of them was specified. System action:
FSA startup for PRINTER fsa_name is canceled. User response:
No response is necessary. System programmer response:
Correct the printer definition in the Printer Inventory for fsa_name. Operator response:
Inform your system programmer that this error occurred. Problem determination:
Items 1, 17, 24. APS619I NOT ALL PARAMETERS REQUIRED TO INITIALIZE AN SNA DEVICE WERE
SPECIFIED IN THE PRINTER INVENTORY FOR fsaname. Explanation:
A parameter was specified which indicates that the printer is to be SNA-attached, but not all the parameters required for SNA attachment were given. To start an SNA-attached printer, all required parameters must be specified. System action:
PSF fails to initialize. User response:
No response is necessary. System programmer response:
Ensure that all required keywords for the SNA-attached printer are specified in the printer definition in the Printer Inventory. For more information, see z/OS Infoprint Server Operation and Administration. The required SNA-attached keywords are:
Operator response:
Inform your system programmer that this error occurred. Problem determination:
Items 1, 17, 24, 26. APS620A ENTER PSF COMMAND OR U – USING THE MVS MODIFY COMMAND. Explanation:
The PSF operator interface has not been initialized. System action:
PSF initialization continues. User response:
No response is necessary. System programmer response:
No response is necessary. Operator response:
You can do one of these:
To initialize the PSF operator interface, enter: where fssname is the name of the PSF FSS as provided in the message. Do not enter a printer name, or the command is rejected. After the PSF operator interface is initialized, you can enter any PSF operator commands. Problem determination:
Items 1, 17, 27. APS621I OPERATOR INTERFACE INITIALIZED FOR product and version. Explanation:
The operator interface has been initialized successfully. All operator commands can now be entered for the PSF version or Download version specified in the message text. System action:
Initialization continues. User response:
No response is necessary. System programmer response:
No response is necessary. Operator response:
Operator commands can now be entered. Problem determination:
None. APS622I NOT ENOUGH STORAGE IS AVAILABLE TO INITIALIZE THE PSF OPERATOR
INTERFACE — STORAGE REQUESTED = size RETURN CODE = code. Explanation:
Not enough storage is available for control blocks or work areas. The message indicates the size of the storage being requested, and the return code is from the MVS GETMAIN macro. System action:
The PSF operator interface is not initialized. PSF initialization continues. User response:
No response is necessary. System programmer response:
Increase the REGION parameter on the procedure used to start PSF. Operator response:
Inform your system programmer that this error occurred. Problem determination:
Items 1, 17, 27. APS623I THE PSF OPERATOR INTERFACE INITIALIZATION WAS UNSUCCESSFUL —
MODULE (module name). Explanation:
The PSF operator interface was not initialized successfully. A functional command initialization module returned a nonzero return code. System action:
The PSF operator interface is not initialized. PSF initialization continues. User response:
No response is necessary. System programmer response:
To determine an appropriate response, see the specific error conditions described in the accompanying messages. Operator response:
Inform your system programmer that this error occurred. Problem determination:
Items 1, 9. APS624I THE PSF OPERATOR INTERFACE IS BEING TERMINATED — MODULE
(module name) HAS TERMINATED. Explanation:
An abend has occurred in a module that has had a previous abend condition. Because the previous abend and this abend involve the same module, no recovery of the operator interface is attempted. System action:
The PSF operator interface is ended. User response:
No response is necessary. System programmer response:
If you suspect a PSF logic error, follow the procedures described in PSF for z/OS: Diagnosis before contacting the IBM Support Center. Operator response:
Inform your system programmer that this error occurred. Problem determination:
Items 1, 9, 11. APS625I THE PSF OPERATOR INTERFACE HAS BEEN TERMINATED. Explanation:
The PSF operator interface has had an unrecoverable error. System action:
The PSF operator interface is ended. User response:
No response is necessary. System programmer response:
If you suspect a PSF logic error, follow the procedures described in PSF for z/OS: Diagnosis before contacting the IBM Support Center. Operator response:
PSF must be purged and restarted to activate the operator interface. Problem determination:
Items 1, 9, 11. APS626I PSF OPERATOR INTERFACE RECOVERY IS {IN PROGRESS |
SUCCESSFUL | UNSUCCESSFUL} — FOR MODULE (module
name). Explanation:
The PSF operator interface has had an error, and recovery is attempted. The error occurred in the named module. System action:
If recovery is successful, normal command processing is continued. If recovery is unsuccessful, the PSF operator interface is ended. User response:
No response is necessary. System programmer response:
To determine the appropriate action, see the problem-determination table. Operator response:
Inform your system programmer that this error occurred. Problem determination:
Items 1, 9, 11. APS627I PSF FSA printer-name HAS BEEN TERMINATED WITH THE
FORCE COMMAND. Explanation:
The operator has issued an MVS MODIFY FORCE command for the specified printer-name. System action:
The Functional Subsystem Application (FSA) for the indicated printer-name has been stopped. User response:
No response is necessary. System programmer response:
No response is necessary. Operator response:
No response is necessary. Problem determination:
Item 1. APS628I SYSTEM COMPLETION CODE system completion code, PSF
ABEND REASON CODE reason code, HAS BEEN DETECTED BY estae
routine. Explanation:
The PSF ESTAE routine detected a PSF abend condition. System action:
Depending on the error condition, PSF attempts either to recover or to end the operator interface. A subsequent PSF message notifies the operator which action was taken. An ESTAE routine creates an SVC dump unless a dump was provided by an earlier routine. User response:
No response is necessary. System programmer response:
Examine the subsequent PSF messages to determine the appropriate response. To interpret the abend code, see System completion codes and PSF abend reason codes. For most abends, you must consult your IBM Support Center representative. For some abends, however, you can recover by increasing the REGION parameter on the startup procedure. Operator response:
Inform your system programmer that this error occurred. Problem determination:
Items 1, 9, 17, 19, 26. APS629I PSF OPERATOR INTERFACE WAS TERMINATED ABNORMALLY. Explanation:
PSF detected an unrecoverable error while evaluating the abend condition. The ESTAE routine should have provided an SVC dump. System action:
Abend processing continues. User response:
No response is necessary. System programmer response:
The contents of the registers at the time of the abend are provided in the SVC dump and register 15 might contain a PSF abend reason code. Save the dump for IBM Support Center use. To interpret the dump, see PSF for z/OS: Diagnosis. To interpret the system completion code, see the publication containing system messages for your operating system. Operator response:
Inform your system programmer that this error occurred. Problem determination:
Items 1, 9, 17, 19, 26. APS630I PSF ESTAE CANNOT EVALUATE SYSTEM COMPLETION CODE system
completion code. ABNORMAL TERMINATION WILL CONTINUE. Explanation:
The PSF ESTAE routine is unable to continue because PSF did not issue the system completion code. System action:
Abend processing continues. User response:
No response is necessary. System programmer response:
To interpret the system completion code, see the MVS system codes publication for your operating system. To interpret the memory dump, see PSF for z/OS: Diagnosis. Save the dump for IBM Support Center use. Operator response:
Inform your system programmer that this error occurred. Problem determination:
Items 1, 9, 17, 19, 26. APS631I A STAPLE JAM HAS OCCURRED WHILE ACCUMULATING SHEETS FOR A
FINISHING OPERATION. PARTIAL OR DUPLICATE PAGES MAY BE PRINTED. Explanation:
The staple mechanism on a printer or post processor has jammed or has caused a physical-media jam. The printer detected and reported an asynchronous intervention-required error with an action code of X'0A' (sense byte 2). For more information about this error, see the printer publications for the printer that reported this error. System action:
PSF resends pages to the printer starting from the jam recovery page counter. Pages might be duplicated during recovery. If repositioning is not supported in the current environment, PSF stops processing the data set. User response:
The printed output might be acceptable. If any pages were duplicated, you might want to resubmit the print request. If the error condition persists, consult your system programmer. System programmer response:
If the error condition persists, follow the procedures described in PSF for z/OS: Diagnosis before contacting the IBM Support Center. Operator response:
See the operator's guide for the printer that reported this error and clear the paper from the printer and post processor. PSF assumes that pages between the jam recovery page counter and the stacked page counter are not damaged and do not need to be reprinted. If any pages between these two printer counters do need to be reprinted, use the JES BACKSPACE command. Problem determination:
Items 1, 8, 18. APS632I DATA IN A FORMDEF RESOURCE IS INCOMPATIBLE WITH THE PRINT
REQUEST: THE OUTPUT CONTAINS TOO MANY SHEETS TO PERFORM THE FINISHING
OPERATION SPECIFIED IN THE MEDIUM FINISHING CONTROL STRUCTURED FIELD. Explanation:
A finishing operation was requested for a collection of sheets, but the number of sheets was too large for the operation. Finishing Operation triplets are specified in the Medium Finishing Control (MFC) structured field. The MFC is specified in the Document Environment Group of the form definition or in a Medium Map. System action:
PSF stops printing and processing the data set. The finishing operation is not applied or incompletely applied. User response:
If the output is not acceptable:
System programmer response:
If an IBM licensed program was used to create the structured fields for the MFC with the error, verify that the input to that program was valid. If the input was valid, see PSF for z/OS: Diagnosis for assistance in determining the source of the problem. If the error involves separator pages or the message data set, use the information provided in the User Response section to correct the error. Operator response:
If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page, for the message data set, or as the default resource for user print data sets in the PSF startup procedure. Inform your system programmer. Problem determination:
Items 1, 2, 13, 15c, 17, 19. APS633I A PARAMETER VALUE IN A FORMDEF RESOURCE IS NOT VALID OR IS
UNSUPPORTED: THE MEDIUM FINISHING CONTROL STRUCTURED FIELD SPECIFIES
AN INCORRECT OR UNSUPPORTED FINISHING OPERATION TYPE FOR THE SELECTED
MEDIA. Explanation:
The operation type field (byte 2) in a Finishing Operation triplet ( X'85') contains an incorrect or unsupported value for the selected media. Finishing Operation triplets are specified in the Medium Finishing Control (MFC) structured field. The MFC is specified in the Document Environment Group of the form definition or in a Medium Map. System action:
Reporting of this exception can be controlled by the Finishing Fidelity triplet in the Presentation Fidelity Control (PFC) command. The PFC command is contained in a form definition. When the Finishing Fidelity triplet sets the continuation rule to STOP (X'01'), PSF stops processing the data set that was being processed at the time of the error and the data set is marked unprintable. PSF releases the current data set back to JES and requests that it be held by the system unless PRTERROR=QUIT is specified on the OUTPUT statement. When the Finishing Fidelity triplet sets the continuation rule to DO NOT STOP (X'02'), one of these occurs:
User response:
If the output is not acceptable:
System programmer response:
If an IBM licensed program was used to create the structured fields for the MFC with the error, verify that the input to that program was valid. If the input was valid, see PSF for z/OS: Diagnosis for assistance in determining the source of the problem. If the error involves separator pages or the message data set, use the information provided in the User Response section to correct the error. Operator response:
If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page, for the message data set, or as the default resource for user print data sets in the PSF startup procedure. Inform your system programmer. Problem determination:
Items 1, 2, 13, 15c, 17, 19. APS634I A PARAMETER VALUE IN A FORMDEF RESOURCE IS NOT VALID OR IS
UNSUPPORTED: THE MEDIUM FINISHING CONTROL STRUCTURED FIELD SPECIFIES
AN INCORRECT OR UNSUPPORTED FINISHING OPERATION REFERENCE CORNER AND
EDGE FOR THE MEDIA BEING FINISHED. Explanation:
The reference corner and edge field (byte 5) in a Finishing Operation triplet ( X'85') contains an incorrect or unsupported value for the media being finished. This can be caused when a supported media size has different supported reference corners and edges depending on which edge of the media is the leading edge. Finishing Operation triplets are specified in the Medium Finishing Control (MFC) structured field. The MFC is specified in the Document Environment Group of the form definition or in a Medium Map. System action:
Reporting of this exception can be controlled by the Finishing Fidelity triplet in the Presentation Fidelity Control (PFC) command. The PFC command is contained in a form definition. When the Finishing Fidelity triplet sets the continuation rule to STOP (X'01'), PSF stops processing the data set that was being processed at the time of the error and the data set is marked unprintable. PSF releases the current data set back to JES and requests that it be held by the system unless PRTERROR=QUIT is specified on the OUTPUT statement. When the Finishing Fidelity triplet sets the continuation rule to DO NOT STOP (X'02'), one of these occurs:
User response:
If the output is not acceptable:
System programmer response:
If an IBM licensed program was used to create the structured fields for the MFC with the error, verify that the input to that program was valid. If the input was valid, see PSF for z/OS: Diagnosis for assistance in determining the source of the problem. If the error involves separator pages or the message data set, use the information provided in the User Response section to correct the error. Operator response:
If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page, for the message data set, or as the default resource for user print data sets in the PSF startup procedure. Inform your system programmer. Problem determination:
Items 1, 2, 13, 15c, 17, 19. APS635I THE COMMAND (command) IS NOT VALID. Explanation:
An incorrect command was entered with the MODIFY command. The command is not supported. System action:
The command is ignored and processing continues with the next command entered. User response:
No response is necessary. System programmer response:
No response is necessary. Operator response:
Enter a valid command. Problem determination:
Item 1. APS636I INCORRECT KEYWORD (keyword) SPECIFIED FOR COMMAND
(command). Explanation:
An incorrect keyword was entered with the MODIFY command. The keyword is not supported. System action:
The command is ignored and processing continues with the next command entered. User response:
No response is necessary. System programmer response:
No response is necessary. Operator response:
Enter the command with a valid keyword. Problem determination:
Item 1. APS637I PROCESSING OF THE FORCE COMMAND FOR PSF FSA printer name HAS
BEEN TERMINATED. THE FSA HAS ALREADY BEGUN TERMINATING. Explanation:
The operator has issued an MVS MODIFY FORCE for a PSF printer that is already in the process of stopping. System action:
The MODIFY FORCE command for the indicated printer name has been discarded by PSF. The stop processing already in progress is completed to attain the results desired by the discarded MODIFY FORCE command. User response:
No response is necessary. System programmer response:
No response is necessary. Operator response:
Enter the command with a valid keyword. Problem determination:
Item 1. APS638I NO COMMAND SPECIFIED — command-text. Explanation:
No command is associated with the data entered. Command-text is the data that was entered. The last character of command-text was the last position checked before PSF determined that no correct command was present. System action:
The command is ignored and processing continues with the next command entered. User response:
No response is necessary. System programmer response:
No response is necessary. Operator response:
Enter a valid PSF command. Problem determination:
Items 1, 9, 11. APS639I COMMAND (command) {ACCEPTED | QUEUED}. Explanation:
The PSF command has been accepted, or the command has been queued for later processing. When the command is accepted, the functional processor is called to process the command. When the command is queued, the command is placed on either an FSS-level queue or an FSA-level queue. All queued commands in which the printer-name is specified are queued on the FSA-level queue. Commands issued without the printer-name are queued on the FSS-level queue. System action:
PSF continues processing the data. User response:
No response is necessary. System programmer response:
No response is necessary. Operator response:
No response is necessary. Problem determination:
Item 1. APS640I PARAMETER parameter in KEYWORD keyword REQUIRES
A PRINTER NAME. Explanation:
A printer name is expected, but no printer is specified. System action:
The command is ignored and processing continues with the next command entered. User response:
No response is necessary. System programmer response:
No response is necessary. Operator response:
Enter the command again, with a printer name. Problem determination:
Item 1. APS641I A MECHANISM EXCEPTION OCCURRED THAT PREVENTS A FINISHING
OPERATION FROM BEING APPLIED. Explanation:
The finishing mechanism on a printer or post processor has an intervention-required condition. The printer detected and reported an asynchronous intervention-required error with an action code of X'0A' (sense byte 2). For more information about this error, see the printer publications for the printer that reported this error. System action:
PSF resends pages to the printer starting from the jam recovery page counter. Pages might be duplicated during recovery. If repositioning is not supported in the current environment, PSF stops processing the data set. User response:
The printed output might be acceptable. If any pages were duplicated, you might want to resubmit the print request. If the error condition persists, consult your system programmer. System programmer response:
If the error condition persists, follow the procedures described in PSF for z/OS: Diagnosis before contacting the IBM Support Center. Operator response:
See the operator's guide for the printer that reported this error and clear the paper from the printer and post processor. PSF assumes that pages between the jam recovery page counter and the stacked page counter are not damaged and do not need to be reprinted. If any pages between these two printer counters do need to be reprinted, use the JES BACKSPACE command. Problem determination:
Items 1, 8, 18. APS642I THE MEDIUM FINISHING CONTROL (MFC) STRUCTURED FIELD
IN THE DOCUMENT ENVIRONMENT GROUP SPECIFIES FINISHING OPERATION TRIPLETS
THAT ARE INCOMPATIBLE WITH THE FINISHING OPERATION TRIPLETS SPECIFIED
ON THE MFC STRUCTURED FIELD IN A MEDIUM MAP. Explanation:
The Medium Finishing Control (MFC) structured field is specified in both the Document Environment Group and in the Medium Map and contain Finishing Operation triplets that are incompatible. Compatible combinations of finishing operations are specific to a particular presentation device. When the element identifier (bytes 16-17) in the formatted sense message (APS830I) is not zero, the printer might provide the number of one of these error conditions that caused the exception to be reported:
The MFC is specified in the Document Environment Group of the form definition or in a Medium Map. System action:
Reporting of this exception can be controlled by the Finishing Fidelity triplet in the Presentation Fidelity Control (PFC) command. The PFC command is contained in a form definition. When the Finishing Fidelity triplet sets the continuation rule to STOP (X'01'), PSF stops processing the data set that was being processed at the time of the error and the data set is marked unprintable. PSF releases the current data set back to JES and requests that it be held by the system unless PRTERROR=QUIT is specified on the OUTPUT statement. When the Finishing Fidelity triplet sets the continuation rule to DO NOT STOP (X'02'), one of these occurs:
User response:
If the output is not acceptable:
System programmer response:
If an IBM licensed program was used to create the structured fields for the MFC with the error, verify that the input to that program was valid. If the input was valid, see PSF for z/OS: Diagnosis for assistance in determining the source of the problem. If the error involves separator pages or the message data set, use the information provided in the User Response section to correct the error. Operator response:
If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page, for the message data set, or as the default resource for user print data sets in the PSF startup procedure. Inform your system programmer. Problem determination:
Items 1, 2, 13, 15c, 17, 19. APS643I DATA IN A FORMDEF RESOURCE IS INCOMPATIBLE WITH THE PRINT
REQUEST: THE OUTPUT CONTAINS TOO MANY SHEETS TO PERFORM THE FINISHING
OPERATION SPECIFIED IN THE MEDIUM FINISHING CONTROL STRUCTURED FIELD. Explanation:
A finishing operation was requested for a collection of sheets, but the number of sheets was too large for the operation. Finishing Operation triplets are specified in the Medium Finishing Control (MFC) structured field. The MFC is specified in the Document Environment Group of the form definition or in a Medium Map. System action:
PSF stops processing the current data set, releases it back to JES, and requests that it be held by the system unless PRTERROR=QUIT is specified on the OUTPUT statement. User response:
If the output is not acceptable:
Either contact your operator to determine which printer the data set can be rerouted to or ask the operator to purge the job so you can resubmit the print request. System programmer response:
If an IBM licensed program was used to create the structured fields for the MFC with the error, verify that the input to that program was valid. If the input was valid, see PSF for z/OS: Diagnosis for assistance in determining the source of the problem. If the error involves separator pages or the message data set, use the information provided in the User Response section to correct the error. Operator response:
If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page, for the message data set, or as the default resource for user print data sets in the PSF startup procedure. Inform your system programmer. If you are running under JES, use the JES commands to release the data set to a printer that supports the finishing operation. For information about the command to use to release the data set, see the publication containing JES commands for your operating system. Problem determination:
Items 1, 2, 13, 15c, 17, 19. APS644I MIXED SIZES OF PHYSICAL MEDIA WERE SELECTED TO BE FINISHED
BUT THE PRINTER DOES NOT SUPPORT FINISHING ON A GROUP OF SHEETS OF
DIFFERENT SIZES. Explanation:
A finishing operation was requested for a collection of sheets of mixed sizes, but the device requires all of the sheets in the collection to be the same size. Finishing Operation triplets are specified in the Medium Finishing Control (MFC) structured field. The MFC is specified in the Document Environment Group of the form definition or in a Medium Map. System action:
PSF stops printing and processing the data set. The finishing operation is not applied or is incompletely applied. User response:
If the output is not acceptable:
System programmer response:
If an IBM licensed program was used to create the structured fields for the MFC with the error, verify that the input to that program was valid. If the input was valid, see PSF for z/OS: Diagnosis for assistance in determining the source of the problem. If the error involves separator pages or the message data set, use the information provided in the User Response section to correct the error. Operator response:
If this message displays on the operator's console, it indicates that the resource containing the error is defined for a separator page, for the message data set, or as the default resource for user print data sets in the PSF startup procedure. Inform your system programmer. Problem determination:
Items 1, 2, 13, 15c, 17, 19. APS645I PARAMETER parameter IS NOT SUPPORTED. Explanation:
A parameter is specified that PSF does not support. System action:
The command is ignored and processing continues with the next command entered. User response:
No response is necessary. System programmer response:
No response is necessary. Operator response:
Enter the command again, without the unsupported parameter. Problem determination:
Item 1. APS646I THE KEYWORD (keyword) IS MUTUALLY EXCLUSIVE WITH
ANOTHER KEYWORD SPECIFIED IN COMMAND (command). Explanation:
Of the keywords specified in this command, two of them cannot both be specified in the same command. System action:
The command is ignored and processing continues with the next command entered. User response:
No response is necessary. System programmer response:
No response is necessary. Operator response:
Enter the command again, with the correct keywords specified. Problem determination:
Item 1. APS647I keyword CANNOT BE SPECIFIED WITH keyword parameter —
keyword IGNORED. Explanation:
The command contains (a) a keyword and (b) a particular combination of keyword and parameter. This particular keyword cannot be used in the same command with this combination of keyword and parameter. System action:
The keyword is ignored and defaults are used. User response:
No response is necessary. System programmer response:
No response is necessary. Operator response:
If different keywords are required, enter the command again. For more information about the keywords, see PSF for z/OS: Diagnosis. Problem determination:
Item 1. APS648I DUPLICATE KEYWORD (keyword) ENTERED FOR COMMAND
(command). Explanation:
A keyword was entered more than once for the same command. System action:
The command is ignored and processing continues with the next command entered. User response:
No response is necessary. System programmer response:
No response is necessary. Operator response:
Enter the command in the correct format. Problem determination:
Item 1. APS649I KEYWORD EXPECTED BUT NOT FOUND — command-text. Explanation:
A keyword was expected on a command, but command-text was found instead. Command-text is the data that was entered. The last character of command-text was the last position checked before PSF determined that no correct keyword was present. System action:
The command is ignored and processing continues with the next command entered. User response:
No response is necessary. System programmer response:
No response is necessary. Operator response:
Enter the correct format of the command. Problem determination:
Item 1. APS650I KEYWORDS ARE NOT ALLOWED WITH COMMAND (command). Explanation:
A command was specified with keywords. This command does not allow keywords. System action:
The command is ignored and processing continues with the next command entered. User response:
No response is necessary. System programmer response:
No response is necessary. Operator response:
Enter the command again without the keywords. Problem determination:
Item 1. APS651I KEYWORD REQUIRED FOR COMMAND (command). Explanation:
A command was entered without keywords. This command requires keywords. System action:
The command is ignored and processing continues with the next command entered. User response:
No response is necessary. System programmer response:
No response is necessary. Operator response:
Enter the command again with the required keywords. Problem determination:
Item 1. APS652I THE PARAMETER STATUS=TCPIP AND THE KEYWORDS SCOPE, EVENT,
AND INTV ARE MUTUALLY EXCLUSIVE IN THE COMMAND DISPLAY. Explanation:
Both the STATUS=TCPIP parameter and one or more of the keywords SCOPE, EVENT, and INTV are specified in the DISPLAY command. The keywords SCOPE, EVENT, and INTV can be specified only when STATUS=AFPDIST. System action:
The command is ignored and processing continues with the next command entered. User response:
No response is necessary. System programmer response:
No response is necessary. Operator response:
Enter the command again, specifying either:
Problem determination:
Item 1. APS653I THE DISPLAY REQUEST FOR component display_type CANNOT
BE PERFORMED BECAUSE NO TCP/IP DESTINATION IS ACTIVE. Explanation:
The request for a DISPLAY command cannot be performed because there are no TCP/IP printers active. component is the component or function, such as TCPIP, used for the DISPLAY command. display_type is the type of display, such as STATUS, requested from the DISPLAY command. System action:
The command is ignored and processing continues with the next command entered. User response:
No response is necessary. System programmer response:
No response is necessary. Operator response:
Make sure that the printer for which you want to issue the command is active and enter the command again. Problem determination:
Item 1. APS654I THE DISPLAY REQUEST FOR component display_type FOR
FSA NAME fsa_name IS NOT VALID. THIS DESTINATION IS attachment AND
A TCP/IP-ATTACHED DESTINATION IS REQUIRED. Explanation:
The request for a DISPLAY command cannot be performed because the destination for which it is requested is not TCP/IP-attached. The component is the component or function, such as TCPIP, used for the DISPLAY command. The display_type is the type of display, such as STATUS, requested from the DISPLAY command. The attachment is the type of attachment for the destination, which can be CHANNEL-ATTACHED, SNA-ATTACHED or UNKNOWN-ATTACHMENT. System action:
The command is ignored and processing continues with the next command entered. User response:
No response is necessary. System programmer response:
No response is necessary. Operator response:
Enter the command for a destination that is TCP/IP-attached. Problem determination:
Item 1. APS655I THE KEYWORDS EVENT=, SCOPE=, and INTV= MUST BE SPECIFIED
WITH KEYWORD STATUS=AFPDP. Explanation:
The keywords EVENT, SCOPE, and INTV can be used only on the MODIFY command with the DISPLAY parameter and the keyword STATUS=AFPDP. System action:
The command is ignored and processing continues with the next command entered. User response:
No response is necessary. System programmer response:
No response is necessary. Operator response:
If you entered a command other than MODIFY DISPLAY STATUS=AFPDP, reenter the command without the SCOPE, EVENT, or INTV keywords. If you meant to enter the command MODIFY DISPLAY STATUS=AFPDP, reenter the command and ensure that the STATUS=AFPDP keyword is included in the command. Problem determination:
Item 1. APS656I THE COMMAND DISPLAY STATUS=AFPDP CANNOT BE PROCESSED BECAUSE
THERE ARE NO JOBS ON THE SPOOL. Explanation:
The command MODIFY DISPLAY STATUS=AFPDP can be processed only while AFP Download Plus is processing a job. System action:
If the value of the SCOPE keyword is ONCE (the default), the command is ignored. Otherwise, the command is queued for the next available job. User response:
No response is necessary. System programmer response:
No response is necessary. Operator response:
If the value of the SCOPE keyword is ONCE, reenter the command while AFP Download Plus is processing a job. Otherwise, no response is necessary. Problem determination:
Item 1. APS661I INCORRECT PARAMETER (parameter) SPECIFIED FOR KEYWORD
(keyword) IN COMMAND (command). Explanation:
A parameter specified for a keyword is not valid. System action:
The command is ignored and processing continues with the next command entered. User response:
No response is necessary. System programmer response:
No response is necessary. Operator response:
Enter the command again, with the correct parameter for the keyword. Problem determination:
Item 1. APS664I THE PARAMETER (parameter) IS MUTUALLY EXCLUSIVE
WITH ANOTHER PARAMETER SPECIFIED IN KEYWORD (keyword) IN
COMMAND (command). Explanation:
Two parameters have been specified that cannot be specified in the same keyword. System action:
The command is ignored and processing continues with the next command entered. User response:
No response is necessary. System programmer response:
No response is necessary. Operator response:
Enter the command again, with consistent keywords specified. Problem determination:
Item 1. APS667I DUPLICATE PARAMETER (parameter) ENTERED FOR KEYWORD
(keyword) IN COMMAND (command). Explanation:
A parameter was specified more than once in the keyword. System action:
The command is ignored and processing continues with the next command entered. User response:
No response is necessary. System programmer response:
No response is necessary. Operator response:
Enter the command without a duplicate parameter for the keyword. Problem determination:
Item 1. APS668I A DELIMITER (delimiter) WAS FOUND IN
THE COMMAND WHERE A PARAMETER WAS EXPECTED - COMMAND TEXT (command-text). Explanation:
A delimiter was found where a parameter was expected. The last character of the command-text data is the incorrect delimiter. System action:
The command is ignored and processing continues with the next command entered. User response:
No response is necessary. System programmer response:
No response is necessary. Operator response:
Enter the command again, in the correct format. Problem determination:
Item 1. APS669I NO PARAMETERS SPECIFIED FOR KEYWORD (keyword) IN
COMMAND (command). Explanation:
A keyword cannot be entered without its associated parameters. System action:
The command is ignored and processing continues with the next command entered. User response:
No response is necessary. System programmer response:
No response is necessary. Operator response:
Enter the command again, with the correct keyword parameters. Problem determination:
Item 1. APS670I UNBALANCED PARENTHESES — command-text. Explanation:
An ending parenthesis is missing from a command. Command-text was the data that was entered. The last character of command-text was the last position checked before PSF determined that a correct parameter list was not present. System action:
The command is ignored and processing continues with the next command entered. User response:
No response is necessary. System programmer response:
No response is necessary. Operator response:
Enter the command and the keyword parameter list in the correct format. Problem determination:
Item 1. APS671I PARAMETER FOUND WHERE PRINTER NAME EXPECTED — command-parameter. Explanation:
A command was entered without the printer name. The command was entered as command,parameter, but it should be entered as command,prtnnnn,parameters if a printer name is to be specified. If a printer name is not to be specified, it should be entered as command,,parameters. System action:
The command is ignored and processing continues with the next command entered. User response:
No response is necessary. System programmer response:
No response is necessary. Operator response:
Enter the command again, with a printer name or with a comma to occupy the position of the printer name. Problem determination:
Item 1. APS672I PARAMETER parameter IS NOT SUPPORTED BY THE AFP DOWNLOAD PLUS FEATURE
OF PSF. Explanation:
A parameter is specified that AFP Download Plus does not support. System action:
The command is ignored and processing continues with the next command entered. User response:
No response is necessary. System programmer response:
No response is necessary. Operator response:
Enter the command again, without the unsupported parameter. Problem determination:
Item 1. APS683I PRINTER NAME CANNOT BE SPECIFIED FOR A PSF COMMAND DURING
INITIALIZATION. Explanation:
The reply for message APS620A specified the printer name in the command. During initialization, the printer name cannot be specified with any command. These commands take effect for the entire FSS; therefore the printer name is incorrect. System action:
The command is ignored and processing continues with the next command entered. User response:
No response is necessary. System programmer response:
No response is necessary. Operator response:
Enter the command without the printer name. Problem determination:
Item 1. APS684I PRINTER NAME (printer-name) IS NOT VALID IN COMMAND
(command). Explanation:
The printer name specified is not valid. The valid format of a printer name is PRTnnnn. System action:
The command is ignored and processing continues with the next command entered. User response:
No response is necessary. System programmer response:
No response is necessary. Operator response:
Enter the correct format of the printer name. Problem determination:
None. APS685I PRINTER NAME CANNOT BE SPECIFIED FOR COMMAND (command). Explanation:
A command was specified with a printer name, and the printer name parameter is not valid with this command. System action:
The command is ignored and processing continues with the next command entered. User response:
No response is necessary. System programmer response:
No response is necessary. Operator response:
Enter the command again without a printer name. Problem determination:
Item 1. APS686I PRINTER NAME IS REQUIRED FOR COMMAND (command). Explanation:
A command was specified without a printer name, and a printer name is required with this command. System action:
The command is ignored and processing continues with the next command entered. User response:
No response is necessary. System programmer response:
No response is necessary. Operator response:
Enter the command again, with a printer name. Problem determination:
Item 1. APS687I PRINTER NAME CANNOT BE SPECIFIED FOR COMMAND (command)
WITH PARAMETER (parameter). Explanation:
The printer name was specified for a command, but the parameter specified with this command does not allow the printer name to be specified. System action:
The command is ignored and processing continues with the next command entered. User response:
No response is necessary. System programmer response:
No response is necessary. Operator response:
Enter the command again without a printer name. Problem determination:
Item 1. APS690I THE DISPLAY REQUEST FOR component display_type WAS
NOT PERFORMED BECAUSE NO TCP/IP PRINTER WAS ACTIVE. Explanation:
The request for a DISPLAY command could not be performed because there are no TCP/IP printers active. component is the component or function, such as TCPIP, used for the DISPLAY command. display_type is the type of display, such as STATUS, requested from the DISPLAY command. System action:
The command is ignored and processing continues with the next command entered. User response:
No response is necessary. System programmer response:
No response is necessary. Operator response:
Make sure that the printer for which you want to issue the command is active and enter the command again. Problem determination:
Item 1. APS691I NOT ENOUGH STORAGE TO PROCESS COMMAND QUEUES — STORAGE
REQUESTED = storage requested, RETURN CODE = return code. Explanation:
Additional storage was required to process the command queues, but this storage was not available. The return code is from the GETMAIN macro. System action:
The command is ignored and processing continues with the next command entered. User response:
No response is necessary. System programmer response:
Increase the REGION parameter on the startup procedure. Operator response:
Inform your system programmer that this error occurred. Problem determination:
None. APS692I THE QEDIT REQUEST WAS UNSUCCESSFUL — RETURN CODE (return
code). Explanation:
An MVS QEDIT request to change the number of requests that could be queued for this FSS was unsuccessful. The return code is the code returned by the QEDIT macro. System action:
The operator interface is ended with a memory dump. User response:
No response is necessary. System programmer response:
For more information about the return codes from the QEDIT macro, see Problem determination; also see z/OS MVS Diagnosis: Tools and Service Aids. Operator response:
Inform your system programmer that this error occurred. Problem determination:
Items 1, 9, 11. APS693I THE MVS STOP COMMAND
IS NOT VALID FOR THE PSF OPERATOR INTERFACE. Explanation:
An MVS STOP command was entered for the PSF operator interface. The PSF operator interface processes only the MVS MODIFY command. System action:
The command is ignored and processing continues with the next command entered. User response:
No response is necessary. System programmer response:
No response is necessary. Operator response:
Use the MVS MODIFY command to enter PSF commands. Problem determination:
Item 1. APS694I system function UNSUCCESSFUL FOR MODULE module
name, RETURN CODE return code — MODULE (issuing
module). Explanation:
A system function was used to perform some task for the operator interface. The function returned a nonzero return code. System action:
Processing ends with an abend or error message. A subsequent PSF message notifies the operator of the action taken. User response:
No response is necessary. System programmer response:
For information about the return code, see z/OS MVS Diagnosis: Tools and Service Aids. If a memory dump was provided, see System completion codes and PSF abend reason codes. Operator response:
Inform your system programmer that this error occurred. Problem determination:
Items 1, 9, 17, 19, 26. APS695I FREEMAIN UNSUCCESSFUL FOR SUBPOOL subpool, RETURN
CODE return code — MODULE (issuing module). Explanation:
The FREEMAIN was unsuccessful. It returned a nonzero return code. System action:
Processing ends with an abend or an error message. A subsequent PSF message notifies the operator of the action taken. User response:
No response is necessary. System programmer response:
For information about the return code, see z/OS MVS Diagnosis: Tools and Service Aids. If a memory dump was provided, see System completion codes and PSF abend reason codes. Operator response:
Inform your system programmer that this error occurred. Problem determination:
Items 1, 9, 17, 19, 26. APS696I PRINTER NAME CANNOT BE SPECIFIED FOR KEYWORD keyword IN
COMMAND command. Explanation:
The printer name was specified for command command, but keyword keyword specified with this command does not allow the printer name to be specified. System action:
The command is ignored and processing continues with the next command entered. User response:
No response is necessary. System programmer response:
No response is necessary. Operator response:
Enter the command again without a printer name. Problem determination:
Item 1. APS697I PRINTER NAME IS REQUIRED FOR KEYWORD keyword IN
COMMAND command. Explanation:
The printer name was not specified with the keyword keyword used in command command. System action:
The command is ignored and processing continues with the next command entered. User response:
No response is necessary. System programmer response:
No response is necessary. Operator response:
Enter the command again, with the printer name. Problem determination:
Item 1. APS698I THE DISPLAY REQUEST FOR component display_type FOR
PRINTER printer_name IS NOT VALID — THIS PRINTER IS attachment,
HOWEVER, A TCP/IP PRINTER IS REQUIRED. Explanation:
The request for a DISPLAY command could not be performed because the printer for which it was requested was not TCP/IP-attached. The component is the component or function, such as TCPIP, used for the DISPLAY command. The display_type is the type of display, such as STATUS, requested from the DISPLAY command. The attachment is the type of attachment for the printer, which can be CHANNEL-ATTACHED, SNA-ATTACHED or UNKNOWN-ATTACHMENT. System action:
The command is ignored and processing continues with the next command entered. User response:
No response is necessary. System programmer response:
No response is necessary. Operator response:
Enter the command for a printer that is TCP/IP attached. Problem determination:
Item 1. APS699I TCP/IP DISPLAY STATUS Explanation:
This message displays the TCP/IP status. To interpret the output, see PSF for z/OS: Diagnosis. System action:
This message is displayed when requested. PSF processing continues. User response:
No response is necessary. System programmer response:
No response is necessary. Operator response:
No response is necessary. Problem determination:
None. 
|
 Copyright IBM Corporation 1990, 2014 |
