If a GDDM error occurred during printing, QMF displays this message:
GDDM error using nnnnnnnn. See message help for details.
The character string nnnnnnnn in the message represents a GDDM printer nickname. Press the Help key to display the help panel, which contains an explanation of the error. This section discusses some common errors and what you can do to fix them.
If you see a message like this, QMF cannot find a nickname definition for the printer name the user specified. You must set up a nickname definition for the printer name, or supply one that is already defined.
If you see a message like this, QMF was able to find a DD statement for the output. You need to provide a DD statement to your QMF startup EXEC, CLIST, or JCL to specify what to do with output from the nickname.
If you see a message like this, your nickname definition is incorrect. The device token you supplied is not a valid token for the type of GDDM printer for which you created the nickname. For a list of valid device tokens for each family of GDDM printers, see the GDDM System Customization and Administration manual or the GDDM Installation and System Management for OS/390 manual.
If you see a message like this, the output the user is trying to print is not valid for the type of printer defined by the GDDM nickname. Certain types of output, such as QMF charts, are restricted to specific families of GDDM printers. For more information on what families of printers handle your type of output, see the GDDM System Customization and Administration manual or the GDDM Installation and System Management for OS/390 manual.
You might see a message like this when starting QMF. The message indicates that you made a syntax error somewhere in the ADMMNICK specification for the nickname. After you fix the syntax error, reload the ADMADFC GDDM defaults module.
A message like this indicates that the temporary storage or transient data queue (SYSP) to which QMF is attempting to print is closed, or that a DD statement is missing from your startup JCL. Contact your CICS administrator for help with this problem (either modifying the JCL and restarting CICS or opening the queue).
If you see a message like this, QMF cannot find a nickname definition for the printer name the user specified. You must set up a nickname definition for the printer name, or supply one that is already defined.
If you see a message like this, QMF was able to find a DD statement for the output. You need to provide a DD statement to your QMF startup EXEC, CLIST, or JCL to specify what to do with output from the nickname.
If you see a message like this, your nickname definition is incorrect. The device token you supplied is not a valid token for the type of GDDM printer for which you created the nickname. For a list of valid device tokens for each family of GDDM printers, see the GDDM System Customization and Administration manual or the GDDM Installation and System Management for OS/390 manual.
If you see a message like this, the output the user is trying to print is not valid for the type of printer defined by the GDDM nickname. Certain types of output, such as QMF charts, are restricted to specific families of GDDM printers. For more information on what families of printers handle your type of output, see the GDDM System Customization and Administration manual or the GDDM Installation and System Management for OS/390 manual.
You might see a message like this when starting QMF. The message indicates that you made a syntax error somewhere in the ADMMNICK specification for the nickname. After you fix the syntax error, reload the ADMADFC GDDM defaults module.
A message like this indicates that the temporary storage or transient data queue (SYSP) to which QMF is attempting to print is closed, or that a DD statement is missing from your startup JCL. Contact your CICS administrator for help with this problem (either modifying the JCL and restarting CICS or opening the queue).
If you see a message like this, your nickname definition is incorrect. The device token you supplied is not a valid token for the type of GDDM printer for which you created the nickname.
If you see a message like this, the output the user is trying to print is not valid for the type of printer defined by the GDDM nickname. Certain types of output, such as QMF charts, are restricted to specific families of GDDM printers. .
You might see a message like this when starting QMF. The message indicates that you made a syntax error somewhere in the ADMMNICK specification for the nickname.
If you see a message like this, QMF cannot find a nickname definition for the printer name the user specified. You must set up a nickname definition for the printer name, or supply one that is already defined.
If you see a message like this, QMF was able to find a DD statement for the output. You need to provide a DD statement to your QMF startup EXEC, CLIST, or JCL to specify what to do with output from the nickname.
If you see a message like this, your nickname definition is incorrect. The device token you supplied is not a valid token for the type of GDDM printer for which you created the nickname. For a list of valid device tokens for each family of GDDM printers, see the GDDM System Customization and Administration manual or the GDDM Installation and System Management for OS/390 manual.
If you see a message like this, the output the user is trying to print is not valid for the type of printer defined by the GDDM nickname. Certain types of output, such as QMF charts, are restricted to specific families of GDDM printers. For more information on what families of printers handle your type of output, see the GDDM System Customization and Administration manual or the GDDM Installation and System Management for OS/390 manual.
You might see a message like this when starting QMF. The message indicates that you made a syntax error somewhere in the ADMMNICK specification for the nickname. After you fix the syntax error, reload the ADMADFC GDDM defaults module.
A message like this indicates that the temporary storage or transient data queue (SYSP) to which QMF is attempting to print is closed, or that a DD statement is missing from your startup JCL. Contact your CICS administrator for help with this problem (either modifying the JCL and restarting CICS or opening the queue).