Vary on pending message on twin ax printer

190 pts.
Tags:
OS/400
Printers
We have a twin ax printer which has had the shuttle and ribbon guide replaced. It prints test pages, but shows status of vary on pending when trying to print from spool file. We have varied on/off with printer on, off and even blew away description, then let it auto config; and we still have the same vary on pending msg.


Software/Hardware used:
we have a model 9402-400 and are at os/400 4r5
1

Answer Wiki

Thanks. We'll let you know when a new response is added.

This problem was solved on 8-31-15 by determining a loose cable existed under the hood of the printer. Hence the message the device would be varied on when it was made ready.

Discuss This Question: 13  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • Splat
    What sort of messages are you getting when you try to vary it on?
    12,915 pointsBadges:
    report
  • azohawk

    We had a sitution similar a few weeks ago following a power blip. There was a converter in the data center that needed to be rebooted and we had to reconfig the (physical) printers to the correct "port" on the controller. (early Monday morning and my mind is still mush-so I am going to use the work port-but I don't think that is the correct term-but I'm drawing a blank on the proper term)

    4,055 pointsBadges:
    report
  • ToddN2000
    What kind of printer and how is it configured? When trying to vary it on, are you flagging the reset option *yes? What is the error ID or message?
    135,305 pointsBadges:
    report
  • Daks
    CPA3387 "Device PRT01 not available. (C R)Writer PRT01 cannot use the device PRT01 because the device is not powered on or varied on or is in use by another job. Before entering a resonse, use the WRKCFGST command to identify the status of the device. Vary on or power on the device if nec essary. Type C to cancel or R to retry.  When I do this I see status "vary on pending".

    190 pointsBadges:
    report
  • Splat
    Correct me if I've got this wrong, but you've deleted the device description & let the system re-create it? 

    If so, have you tried WRKCFGSTS CFGTYPE(*DEV) CFGD(*PRT) to see if, in fact, another job does have it allocated?
    12,915 pointsBadges:
    report
  • Daks
    I had not, but have now done so and it shows no jobs attached. NOTE: On Friday I was on a screen which I can't get back to which showed my other printers having an outq value = to the dev name. PRT01 didn't show an outq. I can't find where to key this detail in at. 
    190 pointsBadges:
    report
  • Daks
    ToddN I don't see a reset option to flag.  This is an IMB6408 printer.
    190 pointsBadges:
    report
  • ToddN2000
    For the RESET option, when you go to vary on the device, prompt for all options. I do not think it shows by default.
    135,305 pointsBadges:
    report
  • Splat
    WRKOUTQ, if you don't specify library or output queue, will show all of the output queues defined on the system. 
    12,915 pointsBadges:
    report
  • TheRealRaven
    What command do you use to start the writer? And what is the name of the printer? (Is it "PRT01"? How do you determine the name associated with your physical printer?)
    36,340 pointsBadges:
    report
  • Daks
    Just now I was getting ready to delete the device again and this time hand key it in as if it was a network printer I was making into a AS-400 printer. On the final page of "dis play device description" screen which shows that PRT01 (which is the printer name) is associated with a job.  However, I can't see this job when I use command, wrkoutq prt01. These are the details "Job name:QSYSARB, User: QSYS, Number, 218636. Any ideas?
    190 pointsBadges:
    report
  • Daks
    Real Raven-- My printer is normally started at weekly IPL.  If it looses power or something during week I use wrkwtr screen to to "Start" or "End."  On rare ocassions I use vary on, vary off commands from wrkcfgsts *dev screen.
    190 pointsBadges:
    report
  • TheRealRaven
    The QSYSARB jobs are system jobs. You'll see them towards the bottom of a WRKACTJOB display if you scroll far enough. In this case, it's holding the *DEVD until some other job wants to use it, i.e., until a writer allocates it. All unused *DEVDs that aren't varied off should show as held by one QSYSARB job or another until some job requests one.

    If it looses power or something during week I use wrkwtr screen to to "Start" or "End."

    In the past, has the printer always been named "PRT01"? There will be a printer *DEVD object, a *MSGQ object, a *OUTQ object and eventually a job (the writer), all probably named "PRT01". If you do WRKOBJ PRT01 and review the *DEVD object, what is its creation date?

    WRKWTR allows you to 'Start' a writer job for a printer device. After you attempt a start, a job named "PRT01" should run. If it fails, it should spool a joblog. What message IDs show in the joblog? Only error messages need to be posted.
    36,340 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.

Following

Share this item with your network: