Printer problems with workstation ID

[Guest.Visitor]

I have a printer session with a static workstation ID that will not start. Using CA V3R1M3 (latest SP) connecting to a 620 AS400 OS V4R2 via TCP/IP. When I set the workstation ID in the printer configuration on the PC to V011782 it attempts to open a session then returns to a blank screen; however, if I change the ID to V11783 it does work. V011782 has worked before as resent as yesterday. I can recreate this on other PCs using the V011782 number, so it looks like an AS400 problem, not a PC problem. Here is what I have done… I deleted the device and OUTQ to let them autoconfig (this is turned on); it does not create a device or OUTQ when the printer session is started on the PC. I renamed an existing device and OUTQ from V011783 to V011782 and restarted the printer session on the PC with the same results. I watched the IP address in "Work with TCP/IP connection status" I see it open connections then end. In the history log I can see the PC (userid) sign on , start the job, then the job ends with 0 (completed normally) status. I have done a wrkobj on V011782 and there is currently no objects with that name. There are not active jobs running with V011782 noted. I'm stumped. The application we are getting ready to implement is dependent upon 64 printers setup via CA to LPT1 and having their OUTQs stay the same. I need to figure out what has happened here or at least how to fix it. Thanks for any help,Jason

[Guest.Visitor]

Jason, I originally wrote this: Interesting! It sounds at first glance just like what would happen if the device were varied off. But you say you have deleted the device description. Try this, have the device recreate again, and I'm sure you will find the same problem. BUT do a WRKCFGSTS *DEV V011782. What does it say? If varied off, vary it on. It should at least be at vary on pending. But after reading it again: It really sounds like you are not using the device ID you think your are. Double check the device name that is being created under Communication/Configure. It sounds like you may have specified a device that is already communicating. Bill Jason Maples wrote: I have a printer session with a static workstation ID that will not start. Using CA V3R1M3 (latest SP) connecting to a 620 AS400 OS V4R2 via TCP/IP. When I set the workstation ID in the printer configuration on the PC to V011782 it attempts to open a session then returns to a blank screen; however, if I change the ID to V11783 it does work. V011782 has worked before as resent as yesterday. I can recreate this on other PCs using the V011782 number, so it looks like an AS400 problem, not a PC problem. Here is what I have done… I deleted the device and OUTQ to let them autoconfig (this is turned on); it does not create a device or OUTQ when the printer session is started on the PC. I renamed an existing device and OUTQ from V011783 to V011782 and restarted the printer session on the PC with the same results. I watched the IP address in "Work with TCP/IP connection status" I see it open connections then end. In the history log I can see the PC (userid) sign on , start the job, then the job ends with 0 (completed normally) status. I have done a wrkobj on V011782 and there is currently no objects with that name. There are not active jobs running with V011782 noted. I'm stumped. The application we are getting ready to implement is dependent upon 64 printers setup via CA to LPT1 and having their OUTQs stay the same. I need to figure out what has happened here or at least how to fix it. Thanks for any help, Jason [/i]

[Guest.Visitor]

Thanks for the reply. Our vendor figured out that there is an entry in a table that is preventing the ID from connecting. According to them the only way to fix it is with an IPL.