0000826: Prevent RACF and LOGR messages if no log stream for usage logging defined - FLAM Issue Tracker

FLAM® Issue Tracker

View Issue Details [ Jump to Notes ]

[ Issue History ] [ Print ]

ID

Project

Category

View Status

Date Submitted

Last Update

0000826

FL5

1.2 FLCC

public

2016-10-11 10:40

2016-10-11 10:49

Reporter

Falk Reichbott

Assigned To

Rolf-Dieter Euler

Priority

normal

Severity

minor

Reproducibility

always

Status

resolved

Resolution

fixed

Platform

System z

OS

z/OS

OS Version

V2R20

Product Version

5.1.13

Target Version

5.1.13

Fixed in Version

5.1.13

Summary

0000826: Prevent RACF and LOGR messages if no log stream for usage logging defined

Description

Currently FLAM try to connect to log stream FLAM.USAGE if no system variable (&FLOGQLx) defined. This results in a lot of messages from RACF and LOGR is this log stream not defined or the corresponding RACF settings not done.

The customers request to prevent these messages.

Tags

No tags attached.

Relationships

Notes
(0001028) Falk Reichbott (administrator) 2016-10-11 10:45 edited on: 2016-10-11 10:49	The connect to a log stream will now (>5.1.13-15352) only be done if the corresponding system variables defined. e.g. SYS1.PARMLIB(IEASYM00) SYMDEF(&FLOGQL1='FLAM') SYMDEF(&FLOGQL2='USAGE') Additonal the SRB time is now called offload time, which is more platform indepentend.

Issue History
Date Modified	Username	Field	Change
2016-10-11 10:40	Falk Reichbott	New Issue
2016-10-11 10:40	Falk Reichbott	Status	new => assigned
2016-10-11 10:40	Falk Reichbott	Assigned To	=> Rolf-Dieter Euler
2016-10-11 10:45	Falk Reichbott	Note Added: 0001028
2016-10-11 10:45	Falk Reichbott	Status	assigned => resolved
2016-10-11 10:45	Falk Reichbott	Fixed in Version	=> 5.1.13
2016-10-11 10:45	Falk Reichbott	Resolution	open => fixed
2016-10-11 10:49	Falk Reichbott	Note Edited: 0001028	View Revisions

Copyright © 2000 - 2024 MantisBT Team