G06.24 ReadMe

may a cause deadlock. The system will hang until the affected CPU is
halted.
Recovery
Reload the CPU.
Workaround
Stop the measurement before using SCF to remove a volume.
Solution 10-040810-8690
The Measfh process will abend with Trap %2 if primary and secondary
extents are specified as 1024 or greater.
Recovery
None.
Workaround
Start a measurement with primary and secondary extents of less than
1024.
o OSM Service Provider (T2728)
Solution 10-040726-8180
OSM requires that the named process $ZNET be running as the default
SCP process. The name $ZNET is required. If $ZNET is not running,
OSM will eventually present incorrect information and may fail for
actions requiring SCP. Saveabend files may be created for
unsuccessful attempts to start an alternate SCP process.
Saveabend files may eventually be created for OSM RALPRVD processes.
Recovery
If $ZNET is not running, start a NonStop pair for the $ZNET SCP
process. If possible, add this process to the SCF configuration
database in the kernel subsystem for automatic startup at system
load as a system process. After $ZNET is started, use SCF to abort
and restart OSM if OSM data appears incorrect for I/O adapters and
related components monitored by OSM. If only a few items in OSM are
incorrect, a rediscover action on affected groups in the OSM Service
Connection will suffice for recovery after $ZNET is started or
restarted.
Workaround
There is no real workaround. OSM requires that $ZNET be running as
the default SCP process name before OSM is started. If $ZNET is
found not to be running, use the recovery mechanism listed above.
Prevent the problem by correctly starting $ZNET at system load.
Solution 10-040707-07
Changing the username or password for accessing a maintenance switch
or (IOAM) UPS outside of OSM results in a username/password mismatch
alarm in OSM (and a Device Status attribute value of Down). If the
alarm is deleted without performing the recovery steps, a second
alarm will not be created by a subsequent Rediscovery action. While
a Rediscovery action does not create a second alarm, the action will
fail and display "Username/password mismatch" in the Action Detail
window.
Recovery
Reconfigure the device in OSM by performing a Stop Monitoring
action on the device, then, under the Monitored Service LAN Devices
Page
3
of
21