Search

Discussion Thread 2

Linux Connector Messages 'NOT' in Opslog  (Lessons Learned)

Library Entry

OPS/MVS 12.3: New Features: OPSLOG OJOBNAME, CART & CARTX Data

See OPSLOG Data Record Expansion feature video. OPSLOG – OJOBNAME Display Field OPSLOG - CART Display Field OPSLOG - CARTX Display Field

452882.mp4

Library Entry

OPS/MVS 12.3: New Features: OPSLOG - First Five Rules Fired

– See the “OPSLOG Data Record Expansion” feature video. – Previously, OPSLOG field show only last rule fired. – Now new OPSLOG fields show first 5 rules fired

452879.mp4

Library Entry

OPS/MVS 12.3: New Features: OPSLOG Event Record Expansion

The length of an OPSLOG event record has been increased to allow more information to be provided for each event record: – FIRST FIVE RULES FIRED – OJOBNAME – CART –CARTX

452874.mp4

Discussion Thread 4

New OPSLOG dataset activation stuck in PendAct status

Discussion Thread 4

OPSLOG - Can "log_name" be passed to a started task?

Discussion Thread 3

OPSLOG Archive Process 12.2  Setup

Discussion Thread 3

OPARLGCR Control Statements

Discussion Thread 6

OPSMVS Suppression - Can I delete a message a message out of the OPSLOG when a message meets a certain criteria?

Library Entry

CA OPS/MVS Event Management and Automation Tech Tip: At IPL time CA OPS/MVS could produces the following error message: OPS3126E DYNAMIC ALLOCATION FAILED; DSNAME=SYS1.OPS.OPAMSVDB, RC=4, ERROR CODE=

Problem: At IPL time CA OPS/MVS could produces the following error message: OPS3126E DYNAMIC ALLOCATION FAILED , RC=4, ERROR CODE=X'1708', INFO CODE=X'0002', DDNAME= OPAMSVDB , DSNAME= SYS1.OPSMVS.OPAMSVDB Solution: The OPSMAIN Address Space shows the dynamic allocation (SVC 99)...