×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
On 08-Jun-2016 12:28 -0500, Jim Hawkins wrote:
Just doing a little out loud thinking. And you may have already
investigated these things:
Does the user acknowledge unloading the image catalog? If so, what
did they do to unload the image catalog?
FWiW responses... inline:
AFaIK the unloads are merely a side-effect of the Power Down System
(PWRDWNSYS) request rather than something explicitly\separately
requested by the user; the unload actions are likely coded as requests
in a system program as pre-requisite work to the actual pwrdwn. My
SWAG: as requests to call QVOIIPL as the apparent Optical component
feature\program to Initiate actions in preparation for pwrdwn\IPL, per
msg CPCBC11 sent F/QVOIIPL T/QWCCSDSC [where that to/program is the CPP
for PWRDWNSYS].
I am not familiar with the from program QWCASDSM, what does it do?
That program is specific to notifying\revealing, from within a
QSYSARB job, the event data that was associated with the request
[including the requesting job] to power down the system; i.e. that will
always be the only program associated-with\sending the msg CPI0995
"PWRDWNSYS command issued with parameters
specified."
On our system it show no usage. How is it called?
System-supplied programs [in the machine-context aka QSYS] are not
tracked for usage; the program is invoked due to an event signaled by
the program QWCCSDSC as Command Processing Program (CPP) for the
PWRDWNSYS command [or by a program invoked by that CPP].
Does the time stamp on the command coincide with when the user
remembers signing on?
The timestamp of the messaging reflects when the initiation of the
pwdwn processing begins [after pre-requisite processing is completed],
not when the actual Command Request of PWRDWNSYS was initiated; with no
catalog unloads transpiring, I expect the timestamps likely would be
much closer than they were in the given scenario, to the msg CPF0901
seemingly logging the command invocation.
AIUI the given joblog shows the request was initiated at ~11:01:37
and then the effect of that request was notified of, via the System
Arbiter job with CPI0995, twelve seconds later at 11:01:49, and nearly
the same time in the [presumed-to-be-accurately] identified-as the
issuing job, via msg CPF0901 F/QWCCSDSC and the process termination
[¿panel with text of, and the?] msg CPC1207 F/QWTMMTRS.
midrange.com
