Q:
ABSTRACT: How does a PSM user specify -odatack=UNBLOCK? Thanks.
SEARCH ARG: AIX/PSM
TOPIC THREAD: PRINT
PSF/AIX
..
I have a user who built a PAGEDEF which most certainly caused output
to be printed off the logical page. Yet, no error messages came out.
The job was submitted via a PDPR command in PSM. I see how if they
used an AIX ENQ command, they could specify the -odatack attribute
and say "=UNBLOCK", which might have caused the messages to flow,
since the PSF/AIX default is apparently -odatack=BLOCK. I don't
see, however, how a PSM user should accomplish the same task. I'd
appreciate your thoughts on this. Thanks.
A:
The PSF parameter datack=unblock corresponds to a pair of attributes
in PSM. One is at the logical printer level, and that is
data-fidelity-problem-reported-supported; the value "all" equates
to PSF's "unblock". The other attribute is at the document or IVD
level, and that is data-fidelity-problem-reported; again the value
"all" equates to "unblock". PSM validates and schedules jobs using
this latter attribute against the former (logical printer) attribute.
For more information, please see PSM Command Reference, S544-3998-02,
page 218 for the logical printer attribute, and pages 158-159 for the
document/IVD attribute.
I hope that helps.
S e a r c h - k e y w o r d s:
AIX PSM DATACK UNBLOCK BLOCK ATTRIBUTE infoprint
WWQA: ITEM: RTA000102915 ITEM: RTA000102915
Dated: 01/1999 Category: PSMAIX
This HTML file was generated 99/06/24~12:43:33
Comments or suggestions?
Contact us