In our shop we did a hardware and OS upgrade from V5R4 to V6R1 15 days back. After, the production system was up, we got an unusual problem with the printer. The printer which worked perfectly after migrating to new system, was asking the user to press OK button before it starts printing. The AS400 system reported below error message,
Otherwise, another option would be to try different values for the Manufacturer type and model (MFRTYPMDL) parameter in your *LAN 3812 DEVD or RMTOUTQ to see if another value will send the PCL Paper Source command for the "correct" paper tray on this printer without having to specify DRAWER(2) in your spooled files. For example, if you are currently using MFRTYPMDL(*HP4000) and WSCST(*NONE) then you could try specifying MFRTYPMDL(*HP5) and MFRTYPMDL(*HP5SI) to see if one of the other choices prints with DRAWER(1).
Operator action required on device XXXXXX.(C R)
From message ID CPA403D.
In order to fix this issue, we first compared both the printer device description , work station customization object and it was same in both. Then, we tried testing both printers, and we found that when the printer was printing from paper tray/drawer 2 it was working fine, however, it was it configured in such a way that it selected drawer 1. But, this is how normally it should work. In order to fix the issue, we just directed the spool files to print from same printer using drawer 2.
Below, is the command to do so.
Option 2 to change next to the spool file
OUTQ(XXXXXX) SAVE(*YES) DRAWER(2)
Otherwise, another option would be to try different values for the Manufacturer type and model (MFRTYPMDL) parameter in your *LAN 3812 DEVD or RMTOUTQ to see if another value will send the PCL Paper Source command for the "correct" paper tray on this printer without having to specify DRAWER(2) in your spooled files. For example, if you are currently using MFRTYPMDL(*HP4000) and WSCST(*NONE) then you could try specifying MFRTYPMDL(*HP5) and MFRTYPMDL(*HP5SI) to see if one of the other choices prints with DRAWER(1).
By changing the Manufacturer type and model, the problem was resolved.
No comments:
Post a Comment