CL Programming

Security Considerations

To debug a program, you must have *CHANGE authority to that program. The *CHANGE authority available by adopting another user's profile is not considered when determining whether a user has authority to debug a program. This prevents users from accessing program data in debug mode by adopting another user's profile.

Additionally, when you are at a user-defined breakpoint of a program that you are debugging with adopted user authority, you have only the authority of your user profile and not the adopted profile authority. You do not have authorities adopted by prior program calls for all breakpoints whether they are added by the Add Breakpoint (ADDBKP) command or are caused by an unmonitored escape message.

Using COPY, SAVE, RESTORE, CRTDUPOBJ, and CHKOBJITG while Debugging

Breakpoints or statement traces may be temporarily removed from a program while the debug function is running if you use certain control language (CL) commands to specify your library or program. Breakpoints and statement traces are restored when the CL command completes running. A CPD190A message is in the job log when the breakpoints or traces are removed; another CPD190A message is in the job log when the breakpoints and statement traces are restored.

Breakpoints or statement traces may be temporarily removed from a program when you use the following CL commands to specify your library:

CHKOBJITG
CPY
CPYLIB
CPROBJ
CRTDUPOBJ
RSTLIB
RSTOBJ
SAVLIB
SAVOBJ
SAVSYS
SAVCHGOBJ
Note:
When the CL commands are running on your program, you may not be able to add breakpoints or add traces to the program. If you enter the Add Breakpoint (ADDBKP) command or the Add Trace (ADDTRC) command when any of the commands are running on your program, you will receive error message CPF7102.


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]