Scenario: Connecting to the *ACCOUNT service
![]()
A typical sequence of tasks is autorecording, turning autorecording off, purging records, and starting recording.
Procedure
- Query the status of z/VM® recording.
As root, issue the following command:
# cat /sys/bus/iucv/drivers/vmlogrdr/recording_status
The results depend on the system, and look similar to the following example:RECORDING COUNT LMT USERID COMMUNICATION EREP ON 00000000 002 EREP ACTIVE ACCOUNT ON 00001812 020 DISKACNT INACTIVE SYMPTOM ON 00000000 002 OPERSYMP ACTIVE ACCOUNT OFF 00000000 020 LINUX31 INACTIVE
- Open /dev/account with
an appropriate application.This action connects the guest to the *ACCOUNT service and starts recording. The entry for *ACCOUNT on guest LINUX31 changes to ACTIVE and ON:
# cat /sys/bus/iucv/drivers/vmlogrdr/recording_status RECORDING COUNT LMT USERID COMMUNICATION EREP ON 00000000 002 EREP ACTIVE ACCOUNT ON 00001812 020 DISKACNT INACTIVE SYMPTOM ON 00000000 002 OPERSYMP ACTIVE ACCOUNT ON 00000000 020 LINUX31 ACTIVE
- Switch autopurge and autorecord off:
# echo 0 > /sys/bus/iucv/drivers/vmlogrdr/account/autopurge
# echo 0 > /sys/bus/iucv/drivers/vmlogrdr/account/autorecording
- Close the device by ending the application
that reads from it and check the recording status.While the connection is INACTIVE, RECORDING is still ON:
# cat /sys/bus/iucv/drivers/vmlogrdr/recording_status RECORDING COUNT LMT USERID COMMUNICATION EREP ON 00000000 002 EREP ACTIVE ACCOUNT ON 00001812 020 DISKACNT INACTIVE SYMPTOM ON 00000000 002 OPERSYMP ACTIVE ACCOUNT ON 00000000 020 LINUX31 INACTIVE
- The next status check shows that some event
created records on the *ACCOUNT queue:
# cat /sys/bus/iucv/drivers/vmlogrdr/recording_status RECORDING COUNT LMT USERID COMMUNICATION EREP ON 00000000 002 EREP ACTIVE ACCOUNT ON 00001821 020 DISKACNT INACTIVE SYMPTOM ON 00000000 002 OPERSYMP ACTIVE ACCOUNT ON 00000009 020 LINUX31 INACTIVE
- Switch recording off:
# echo 0 > /sys/bus/iucv/drivers/vmlogrdr/account/recording
# cat /sys/bus/iucv/drivers/vmlogrdr/recording_status RECORDING COUNT LMT USERID COMMUNICATION EREP ON 000000000 002 EREP ACTIVE ACCOUNT ON 00001821 020 DISKACNT INACTIVE SYMPTOM ON 00000000 002 OPERSYMP ACTIVE ACCOUNT OFF 00000009 020 LINUX31 INACTIVE
- Try to switch it on again, and check whether
it worked by checking the recording status:
# echo 1 > /sys/bus/iucv/drivers/vmlogrdr/account/recording
# cat /sys/bus/iucv/drivers/vmlogrdr/recording_status RECORDING COUNT LMT USERID COMMUNICATION EREP ON 000000000 002 EREP ACTIVE ACCOUNT ON 00001821 020 DISKACNT INACTIVE SYMPTOM ON 00000000 002 OPERSYMP ACTIVE ACCOUNT OFF 00000009 020 LINUX31 INACTIVE
Recording did not start, in the message logs you might find a message:
This kernel message has priority 'debug' so it might not be written to any of your log files.vmlogrdr: recording response: HCPCRC8087I Records are queued for user LINUX31 on the *ACCOUNT recording queue and must be purged or retrieved before recording can be turned on. - Now remove all the records on your *ACCOUNT
queue either by starting an application that reads them from /dev/account or
by explicitly purging them:
# echo 1 > /sys/bus/iucv/drivers/vmlogrdr/account/purge
# cat /sys/bus/iucv/drivers/vmlogrdr/recording_status RECORDING COUNT LMT USERID COMMUNICATION EREP ON 00000000 002 EREP ACTIVE ACCOUNT ON 00001821 020 DISKACNT INACTIVE SYMPTOM ON 00000000 002 OPERSYMP ACTIVE ACCOUNT OFF 00000000 020 LINUX31 INACTIVE
- Now start recording and check
status again:
# echo 1 > /sys/bus/iucv/drivers/vmlogrdr/account/recording
# cat /sys/bus/iucv/drivers/vmlogrdr/recording_status RECORDING COUNT LMT USERID COMMUNICATION EREP ON 00000000 002 EREP ACTIVE ACCOUNT ON 00001821 020 DISKACNT INACTIVE SYMPTOM ON 00000000 002 OPERSYMP ACTIVE ACCOUNT ON 00000000 020 LINUX31 INACTIVE