ESP Workload Automation

Expand all | Collapse all

Failed Job Message Device Not Ready

  • 1.  Failed Job Message Device Not Ready

    Posted May 05, 2016 10:37 AM

    Does anyone know what the message device not ready indicates on an open system job?



  • 2.  Re: Failed Job Message Device Not Ready

    Posted May 05, 2016 12:27 PM

    Please provide additional information.

    What is the scheduler?

    What is the workload object type?

    Where is the message displayed?  (in CSF, Job output, Agent Logs)



  • 3.  Re: Failed Job Message Device Not Ready

    Posted May 05, 2016 12:45 PM

    I m using ESP.  The job is an NT job.  The message is in CSF.

    I had the server stopped and restarted but that did not help.



  • 4.  Re: Failed Job Message Device Not Ready

    Posted May 05, 2016 01:36 PM

    I'd say start by making sure that the agent is actually "talking" - from a page screen or LMI, do ESPCOM DEST(-)  make sure your agent says this:

     

    BCAPP059        |active|Send OK  13.00.20 05 MAY|

     

    Then take a look for permissions issues at the agent level.  Remember that unless you are using the PASSWORD command to enter user names and passwords, Windows jobs will run as whatever the user is that the agent is running as.

     

    Hope this helps.



  • 5.  Re: Failed Job Message Device Not Ready

    Posted May 06, 2016 08:10 AM

    I tried this and everything looked good - I received the message you indicated.  I'm thinking there was a glitch and by the time I checked this and tried to rerun things were ok. 

     

    I appreciate you help and will keep this command on file for future reference.  Thanks!



  • 6.  Re: Failed Job Message Device Not Ready

    Posted May 05, 2016 01:42 PM

    For kicks, I decided to try running the job again and it worked.  I'm guessing there was a glitch there somewhere.  Thank you for your help and your suggestion - it is much appreciated!



  • 7.  Re: Failed Job Message Device Not Ready

    Posted May 05, 2016 02:22 PM

    Do you have access to the Windows server?

    First I would check the Spool Directory for the Application.Generation directory and look at the job output if any.  What is in the file?

    Next open a Windows Command prompt and navigate to the Log directory and enter the following command.

    findstr "device not ready" *.log

     

    Does the command above find anything?

    I would expect there is at least an entry in the transmitter.log

    If it does open that log and review all messages, there may be something of meaning before or after the message.

     

    If you have not already created an ESP Test PROC to verify agent functionality I would recommend you do that. If you need help setting that up let me know.

    I am not a fan of starting/stopping the agent or the server to "fix" problems, since all that does is mask an issue.

    Define the problem and work on a resolution.

     

    You can also open a Priority 4 "Question About Use" case we CA and see what they say.



  • 8.  Re: Failed Job Message Device Not Ready

    Posted May 06, 2016 08:12 AM

    I checked the log with no results.  The spool only showed the message 'device not ready;.

    Since when I retried submitting the job it ran, I am going to hold on to your suggestion for future reference.  I appreciate your help!



  • 9.  Re: Failed Job Message Device Not Ready

    Posted May 05, 2016 06:12 PM

    Barb,

    It could be due to a piece of storage that is not available. Sign into the NT box and initiate the same script/command with the same user as ESP is trying to do.  

     



  • 10.  Re: Failed Job Message Device Not Ready

    Posted May 06, 2016 08:13 AM

    I do not have access to sign into the box to run the script from there.  However, I will add this to my things to check for any future occurrences of this message.  I do appreciate your help!



  • 11.  Re: Failed Job Message Device Not Ready

    Posted May 06, 2016 09:56 AM

    I always request access to the server if the agent is installed, as it is needed for support and troubleshooting. If they will not give it when there are issues call the server admin and make them troubleshoot.  When they say "I do not have time/knowledge, why should I do it".  You respond "because you did not give me access to the server, so I cannot do my job"

     

    If they are still hesitant to give it to you, then you should at least have the Windows server Admin set up a share with Read access for the Spool and Log files (you may need to update the agentparm file) .  Then you can map a drive to the share to view the files.

     

    If they will not grant you access or create the share then you should create ESP Jobs that provide you with the capability that is required to support the agent.

     

    Additional information can be found in some previous posts:

     

    ESP Check Agent

    https://communities.ca.com/thread/241701148

    System Agent to allow Viewing the Contents of a Script

    https://communities.ca.com/docs/DOC-231150817

    Unix Log file retrieval

    https://communities.ca.com/thread/106938538

     

    You can make modifications to the examples above to provide the functionality that you need.

    If you have any questions please feel free to contact me and I can help you work through it.  My email address is rromanowski@ups.com