Changing the form type on a printer
Admin Rookie
I recently set up a 'stand alone' HP printer attached to a users PC
via a USB cable. I have made this printer their default and created an
IBM session which in turn has created an outq.
I have succesfully ran jobs to this outq but they wont print. Instead
i get the message below....
Message . . . . : Load form type '*STD' device CAROLEPRT writer
CAROLEPRT.
(G B I H R
C)
Cause . . . . . : The file on output queue CAROLEPRT in library
QUSRSYS
requires form type '*STD' to be loaded on device CAROLEPRT. The form
type
for the file was all blanks when '' appears as the form
type.
Possible choices for replying to
message . . . . . . . . . . . . . . . :
Now, from my understanding i need to change the form type so that it
will print everything and anything.
The choices of response are as follows:-
G -- Begin processing the current file after loading the form
type.
B -- Begin processing the current file after loading and aligning the
form
type (no alignment message is sent - same as option 1 on System/
36).
I -- Ignore the request to load the form type. Print the file on
the
current formtype (same as option 0 on System/
36).
H -- Hold the file and print the next file on the output
queue.
R -- Search the output queue for the first available file with the
correct
form type. Reply value R is useful after using the Change Writer
(CHGWTR)
command to change the form type or the output queue of the
writer.
*FILEEND must be specified for the option (OPTION) parameter on the
CHGWTR
command for the change to take
effect.
C -- Cancel the writer (same as option 2 on System/
36).
If i take option 'I', it will happily go away and print my job on the
printer.
Where can i go to set this outq to print all form types?
Am i changing the outq or the writer or the device description?
When i try to change the writer (CHGWTR), nothing really happens.
All print jobs are at HLD status at the minute.
Any help appreciated!
Colin Seftel
If you take option 'G' you won't be prompted again, so long as the form
type of the spooled file is the same (*STD).
Admin Rookie
>
> - Show quoted text -
Colin - that worked. Many thanks.
Rodney Johnson
The reason the form type message is presented is because the printer
device description is new and therefore does not have a valid value for
the formtype that was previously used. This message should be answered
with a 'G' in this condition. Answering with an 'I' is meant only for
conditions where for one instance there is a desire to ignore that the
printer may not have the formtype desired for that spooled file.
Note that there are two other conditions where the form type message may
be presented. If the writer is up and running for the printer and the
system crashes, the last form type used will not get saved in the
printer device description. This will cause the change form type
message to be presented the next time a writer is started to the
printer. The third condition is for PSF printers only. If when ending
a writer to a printer using PSF/400 and the PDJ (print driver job) does
not end in 2 minutes, the writer will end and not save the last form
type used since it is undetermined. Again when the writer is started to
the printer a change form type message will be issued.
FYI, the reason I bring up the replying with 'I' as "bad" is because
many customers who have production continuous form printers that can be
destroyed in a short period of time because of an autoreply list entry
of 'I' for the changes forms message. There is no valid reason for any
system I user to have 'I' as an autoreply value for the change forms
message. If one does not care about the form type used, 'G' is the
proper response.
--
Rodney A Johnson
Working on IBM Smart Business. Former technical team Lead for i5/OS
(AS/400) Spool
Dept 33A
IBM Rochester, Minnesota
The contents of this message express only the sender's opinion.
This message does not necessarily reflect the policy or views of
my employer, IBM. All responsibility for the statements
made in this Usenet posting resides solely and completely with the
sender.
Falco
System Reply Message.
ADDRPYLE SEQNBR(400) MSGID(CPA3394) CMPDTA('PRT01' 1) RPY('G')
You will have to replace the PRT01 with your printer name and maybe
the SEQNBR if it is already used.
You can view the System Reply list with the WRKRPYLE command.
~Falco
cont...@truckdrivingcdljobs.com
Curt Morehouse
W N Morehouse Truck Line, Inc
402-733-2200 x 202
CRPence
> Hey I just upgraded to V6R1 and now all of my printers have changed.
> status. I don't even get the option to reply with G or I like I used
>
Presumably some customization was lost due to the upgrade, and that
customization was not reapplied [perhaps because it was not recorded] as
part of a good System Change Management policy\procedures.
Presumably the issue is per message identifier CPA3394 having a
Default Reply of H=Hold [CHGMSGD DFT()], the spooling Job Description
having Inquiry Message Reply handling [CHGJOBD INQMSGRPY()] established
as defaulting to search the System Reply List (*SYSRPYL), and no entry
in the System Reply List Entries [WRKRPYLE] for that inquiry message.
If in the past that condition had been notified by an inquiry message
for which a reply was awaited, then one possibly is that the *JOBD for
the writer job had been customized via CHGJOBD INQMSGRPY(*RQD); another
that a specific or generic message identifier in the reply list entries
was removed.
The actual spooled joblog of the writer job and a DSPJOB
OUTPUT(*PRINT) of that same writer job might be good places to look to
see about if\how messaging is being performed\handled. The latter,
minimally, to learn what Job Description is used; and the INQMSGRPY()
setting that the job obtained from there.
While the Start Printer Writer (STRPRTWTR) defaults to requesting an
inquiry be sent for Form Type changes per FORMTYPE(*ALL *INQMSG), the
inquiry handling still follows the normal rules; i.e. whatever might
cause a default or alternate reply to be supplied automatically, can
override the intent of "*INQMSG". Note: STRRMTWTR defaults to sending
neither an inquiry nor an informational message per its FORMTYPE(*ALL
*NOMSG) but I do not know the effect; e.g. is the spool file
automatically held.? But since "the message" is being sent, and
apparently an inquiry per the system "automatically replying", the
"*NOMSG" is probably not germane.
Regards, Chuck