Why does message not sent to the activity log with &WRITE LOG=YES?

Document ID:  TEC1941239
Last Modified Date:  08/24/2017
{{active ? 'Hide' : 'Show'}} Technical Document Details

Products

  • CA SOLVE:Access Session Management
  • CA SOLVE:Operations Automation
  • CA NetMaster Network Management for TCP/IP
  • CA NetMaster Network Automation
  • CA NetMaster File Transfer Management
  • CA NetMaster Network Management for SNA
  • CA SOLVE:FTS

Releases

  • CA SOLVE:Access Session Management:Release:5
  • CA SOLVE:Operations Automation:Release:11.9
  • CA NetMaster Network Management for TCP/IP:Release:12.1
  • CA NetMaster Network Management for TCP/IP:Release:12.2
  • CA NetMaster Network Automation:Release:12.1
  • CA NetMaster Network Automation:Release:12.2
  • CA NetMaster File Transfer Management:Release:12.1
  • CA NetMaster File Transfer Management:Release:12.2
  • CA NetMaster Network Management for SNA:Release:12.1
  • CA NetMaster Network Management for SNA:Release:12.2
  • CA SOLVE:FTS:Release:12.1

Components

  • Unicenter SOLVE:Access Session Management:SACCES
  • CA SOLVE:Operations Automation for z/OS:SOPMVS
  • CA NetMaster Network Management for TCP/IP:NMTIP
  • CA NetMaster Network Automation:NMAUTO
  • CA NetMaster File Transfer Management:NFT
  • CA NetMaster Network Management for SNA:NMSNA
  • CA SOLVE:FTS:SFTS
Introduction:

All messages sent to the activity (online) log are going through the logproc ($LOPROC).

As it is created as an OML procedure, it is not possible to alter for custom settings. A logproc exit is provided for this purpose and may be used for messages monitoring from the activity log. It  can be set through the 'Log Exit Name' field in /PARM $NM LOGFILES group.

 

Question:

Why does message not sent to the activity log with &WRITE LOG=YES?

 

Answer:

&WRITE is used to generate a message from a NCL procedure. With LOG=YES parm, it is possible to send the message to the log from any environment except from the LOGP.

For this reason, &WRITE LOG=YES will not send any message if it is executed from a logproc exit running in LOGP.

The workaround consists of submitting another NCL procedure to a background environment from there.

 

Example:

Instead of &WRITE LOG=YES in the logproc exit, use the following statement:

&INTCMD SUB BSYS -EXEC  ncl_proc

ncl_proc  includes  &WRITE LOG=YES

 

Additional Information:

The logproc exit should be used with care in any environment receiving a lot of messages in the log.

Each of them causes the logproc exit to be executed and may impact the performance of the region.

 

 

Please help us improve!

Will this information enable you to resolve your issue?

Please tell us what we can do better.

{{feedbackText.length ? feedbackText.length : '0'}}/255

{{status}}

Not what you were looking for?

Search Again >

Product Information

Support by Product >

Communities

Join a Community >