Control Values › YDBFCCS - Database Coded Character Set › Warning Note

Warning Note

The YDBFCCS Web Option control value is used by both Web Option and EJB Option. If you have both of these products installed, be aware that a change to it affects processing in both products.

YDBGDTA - Debugging Data Flags

YDBGDTA holds the flags that define the type of debugging data you want to retain. This value consists of thirteen Yes or No flags as follows:

• 1: CGI data from client
• 2: HTML data to client
• 3: VT input data
• 4: VT output data
• 5: VT open data
• 6: VT close data
• 7: Script statements
• 8: Dump errors
• 9: Client requests
• 10: Generator
• 11: Print definition
• 12: JIT errors
• 13:Element customization

Shipped Value (Allowed Values)

All flags set to N (each flag can be Y or N)

Usage

The separate flags in the YDBGDTA control value allow you to specify the following debugging options:

1. CGI data from client

   If set to Y, CGI data from the client (browser) to the Web Option server is written to the debug data file.

2. HTML data to client

   If set to Y, HTML data sent from the Web Option server to the client (browser) is written to the debug data file.

3. VT input data

   If set to Y, 5250 data stream sent to the virtual terminal APIs from the Web Option server is written to the debug data file.

4. VT output data

   If set to Y, 5250 data stream sent from the virtual terminal APIs to the Web Option server is written to the debug data file

5. VT open data

   If set to Y, the data used to open the virtual terminal is written to the debug data file.

6. VT close data

   If set to Y, the data used to close the virtual terminal is written to the debug data file.

7. Script statements

   If set to Y, all script statements executed at runtime are written to the debug data file.

8. Dump errors

   If set to Y, all errors in the Web Option runtime result in the errant procedure being dumped to a QPPGMDMP spooled file.

9. Client requests

   If set to Y, client request records denoting different actions performed by the Web Option router and server are written to the debug data file.

10. Generator debugging

    If set to Y, debugging lines are included in the generated skeleton.

11. Print definition

    If set to Y, a spooled file is created when a skeleton is generated, describing the data that was retrieved from the display file

12. JIT errors

    If set to Y, and Just-In-Time errors are dumped to a QPPGMDMP spooled file

13. Element customization

    If set to Y, element customization records are written to the job log of the job running the YGENMLS command.

Warning! Only use debugging data when requested by CA support staff. All values must normally be set to N. Pay attention specifically to flags 1– 4; these can cause performance issues if set to Y. Flag 8 can cause major performance issues if errors are being encountered on an ongoing basis. Additionally, if set to Y, flag 1 results in data that is entered on the web page being written to a file, to include secure items such as passwords.

YBGSSN - Debug Session ID

YDBGSSN holds the 16-character session ID that should be debugged. You can set it to the special values *NONE (meaning that no user jobs will be debugged) or *ALL (meaning that all user jobs will be debugged), or you can set it to a valid 16-character session ID. The specific types of information to trace and debug are held in the YDBGDTA Web Option control value.

Note: The YDBGSSN control value is ignored unless at least one YDBGDTA flag is set to Y.

Shipped Value (Allowed Values)

*ALL (*ALL|*NONE|session-identifier)