"Logging was stopped" error message
search cancel

"Logging was stopped" error message

book

Article ID: 45119

calendar_today

Updated On:

Products

File Master Plus for IMS File Master Plus for DB2 for z/OS

Issue/Introduction

When using File Master Plus for IMS in EDIT mode with selection criteria, the user is getting the error message "Logging was stopped".

Cause

 When using File Master Plus for IMS in EDIT mode with selection criteria, the user is getting the error message "Logging was stopped". When he presses PF1 for more data it says: 
The Change log was stopped because of an internal error. The dataset 'dsn.dsn.change.SYS6884.L0000000' maybe unusable or not contain any data. 
The change log does not exist. So I cannot determine what occurred. 
If we do the same entry with the selection criteria as a browse (rather than update) it works fine. If we do this as an Edit without the selection criteria it works just fine.

Resolution

Use the ISPF Table Utility to edit member CAWKPROF in your ISPF Profile data set and change the following profile variables as noted 
    Set CLOGALC to N (it was blank) 
    Set CLOGDEL to N (it was blank) 
    Set CLOGPOPT to K (it was 1) 
    Set CLOGPRT to N (it was blank) 

Additional Information

CLOGPOPT indicates the desired state of the log file after an edit (Print, Keep, Delete). It is set to a numeric value (such as 1) following certain errors, but that should not be visible to the user, as it is supposed to be changed back to a usable value after the error is processed, based on the values of CLOGPRT, CLOGALC and other variables, including some set during installation (in the Options member). 
•CLOGPRT and CLOGALC represent (respectively) the “Print Current Log” and “New Log Name in next session” options in the “Change Log Processing” panel. They should always be either Y or N, and this is enforced in that panel.