MVS Download started/stopped messages at MVS console.
ITEM: RTA000100907
Q:
ABSTRACT: MVS Download started/stopped messages at MVS console.
My client has just installed PSM with MVS Download. One thing that is
missing is a message to the MVS JES console that can be logged that says
that a job has been MVS Downloaded, whether the job has been sent or is
being sent, etc. Perhaps we don't have something set up.
Is something available like that.....client mentioned exit APUX16 as a
possibility?
Also, clarify for me how the MVS PROC works in MVS Download environment.
If we set up the default resources FORMDEFs and PAGEDEFs in the PROC for
both the printer and MVS Download, then it looks for those resources at
the RS/6K, right? These calls are within the AFPDS being sent down
to the RS/6K, right?
A:
In the MVS Download Guide (G544-5294-00), page 58:
MONITORING DATA-SET TRANSMISSION
"MVS Download issues messages to the console when errors occur during
transmission. MVS Download also issues a message to the SYSLOG data set
when a data set has been transmitted to an AIX system, if the user
requested notification on the NOTIFY keyword of the OUTPUT JCL
statement."
DISPLAYING CURRENT ACTIVITY
"In a JES2 environment, you can use the SDSF printer display command to
display the total and running page/record count of the data set
currently being transmitted by an MVS Download FSA. Note that SDSF
displays the status of the MVS Download FSA only if the MVS Download
feature is performing checkpointing."
Is that the sort of information you're looking for? The MVS Download
book does not mention any exits, but I can check further with Boulder
if the above information isn't sufficient. Please reopen the item
if necessary.
Regarding your second question, if you're sending down line data
through MVS Download to PSF for AIX, the PAGEDEF and FORMDEF object
must reside on the PSF for AIX system in one of the search paths that
PSF knows about. Your PAGEDEF and FORMDEF can be specified on the
JCL OUTPUT card, or the defaults in the PROC can be used. There is
a table in the MVS Download Guide (G544-5294) that shows how to
specify *no* defaults in a JES2 environment (Table 4) -- which is not
what you asked, but just in case... If you're sending line data down
to PSF/AIX, you are not sending AFPDS--it's really the line data
coming down; it will be ACIF'ed on PSF/AIX with the PAGEDEF and FORMDEF
to produce AFPDS on AIX. You can also send down AFPDS with MVS
Download, but AFPDS does not use a PAGEDEF, as it is fully composed
already; it still needs a FORMDEF. Does that make sense?
Q:
Sorry, forgot to mention in my question, we have looked at the manual
re: the above passages. The 2nd one, the client is aware of and uses,
but it is not a console message, you have to go into SDSF to see the
activity.
The 1st one will require JCL changes to add to the OUTPUT statement the
NOTIFY parameter. That will require a lot of work. They were looking
for something that is like what happens today when a job starts, the
console messages says it has started and it says when it ends. I
believe that it also says when something has printed on PRTxxx also.
All of the above comes out as console messages which is printed out and
logged. This way, they can go back and see if a job ran or printed.
With MVS Download, there is no way to document that a job has been sent
to the RS/6K or we don't have it set up.
In regards to the PROC, the client is sending both AFPDS, so that's
fully composed, and line data which according to your reply will use
the FORMDEF resource local on the RS/6K. Yes, we understand.
We have seen a previous ASKQ item that states that TCP/IP does not use
IPDS conversation so the resource control under IPDS is not available
with TCP/IP MVS Download. So manual resource synchronization will be
required to match resources at host and RS/6K. This is contrary to what
we have been marketing as a highlight of AFP so this not consistent but
I guess this is function of using TCP/IP rather than SNA.
A:
Regarding the logging of messages to the MVS JES console, it looks
like APAR OW20079 is just what you are looking for. It will enable
a HASP150 to be sent to the host when a job becomes active. Also,
with this APAR, the customer will not need to add the NOTIFY
parameter to their JCL.
Unfortunately, there is no mechanism to report back to the host that
the job has completed printing. Once the job is spooled to the RS/6K,
control of the job has been passed to PSF/AIX. If the customer wants
to track which jobs have been printed, he will have to do so at the
PSF/AIX level.
Your assessment of SNA vs TCP/IP is correct. Hopefully you are now
clear on how TCP/IP limits AFP capabilities.
S e a r c h - k e y w o r d s:
MVS DOWNLOAD PSF/AIX PSF/6000 MESSAGES PSM RESOURCES CONSOLE xpsf6000
WWQA: ITEM: RTA000100907 ITEM: RTA000100907
Dated: 11/1999 Category: PSMAIX
This HTML file was generated 2000/11/30~13:34:06
Comments or suggestions?
Contact us