SGI_Indy
asked on
AS/400 and Zebra P4T
Ok, I have a problem. My company has been using an AS/400 to manage the warehouse. We currently have some Zebra QL420 printers which print out barcode labels for our replenishment team. Due to the advancement in wireless technology, we are going forced to look at new printers, namely, the Zebra P4T. Now, when I setup the OutQ for the printer, I come to a line called 'Manufacturer type and model'. I filled this in with the normal *WSCST and the next lines with our custom label code. Problem is, Zebra is telling me that this code is telling the P4T to go to 'gap' sensing on the labels instead of 'bar'. They said I have to change that and I have no clue how. Any ideas would be greatly appreciated!
ASKER
Queue: RPTEST3 Library: QUSRSYS
Status:
Writer active . . . . . . . . . . . : Y
Writer name(s) if active . . . . . . : RPTEST3
Output queue held . . . . . . . . . : N
Maximum spooled file size:
Number of pages . . . . . . . . . . : *NONE
Starting time . . . . . . . . . . . :
Ending time . . . . . . . . . . . . :
Writers to autostart . . . . . . . . . : 1
Display any file . . . . . . . . . . . : *NO
Job separators . . . . . . . . . . . . : 0
Operator controlled . . . . . . . . . : *YES
Order of files on queue . . . . . . . : *FIFO
Data queue . . . . . . . . . . . . . . : *NONE
Library . . . . . . . . . . . . . . :
Queue: RPTEST3 Library: QUSRSYS
Authority to check . . . . . . . . . . : *OWNER
Remote system . . . . . . . . . . . . : *INTNETADR
Remote printer queue . . . . . . . . . : RAW
Queue for writer messages . . . . . . : QSYSOPR
Library . . . . . . . . . . . . . . : *LIBL
Connection type . . . . . . . . . . . : *IP
Internet address . . . . . . . . . . . : 10.10.30.130
Destination type . . . . . . . . . . . : *OTHER
Host print transform . . . . . . . . . : *YES
Queue: RPTEST3 Library: QUSRSYS
Manufacturer type and model . . . . . : *WSCST
Workstation customizing object . . . . : Z4XIWSCST
Library . . . . . . . . . . . . . . : TLABARCODE
Image configuration . . . . . . . . . : *NONE
Destination options . . . . . . . . . : *NONE
Print separator page . . . . . . . . . : *NO
User defined option . . . . . . . . . : *NONE
User defined object:
Object . . . . . . . . . . . . . . . : *NONE
Library . . . . . . . . . . . . . :
Object type . . . . . . . . . . . . :
User driver program . . . . . . . . . : *NONE
Library . . . . . . . . . . . . . . :
Well, that is what I thought as well, but I am not even able to locate what is wrong and where. I am not an AS/400 person :) so I know very little about it.
Thanks for any help!
Status:
Writer active . . . . . . . . . . . : Y
Writer name(s) if active . . . . . . : RPTEST3
Output queue held . . . . . . . . . : N
Maximum spooled file size:
Number of pages . . . . . . . . . . : *NONE
Starting time . . . . . . . . . . . :
Ending time . . . . . . . . . . . . :
Writers to autostart . . . . . . . . . : 1
Display any file . . . . . . . . . . . : *NO
Job separators . . . . . . . . . . . . : 0
Operator controlled . . . . . . . . . : *YES
Order of files on queue . . . . . . . : *FIFO
Data queue . . . . . . . . . . . . . . : *NONE
Library . . . . . . . . . . . . . . :
Queue: RPTEST3 Library: QUSRSYS
Authority to check . . . . . . . . . . : *OWNER
Remote system . . . . . . . . . . . . : *INTNETADR
Remote printer queue . . . . . . . . . : RAW
Queue for writer messages . . . . . . : QSYSOPR
Library . . . . . . . . . . . . . . : *LIBL
Connection type . . . . . . . . . . . : *IP
Internet address . . . . . . . . . . . : 10.10.30.130
Destination type . . . . . . . . . . . : *OTHER
Host print transform . . . . . . . . . : *YES
Queue: RPTEST3 Library: QUSRSYS
Manufacturer type and model . . . . . : *WSCST
Workstation customizing object . . . . : Z4XIWSCST
Library . . . . . . . . . . . . . . : TLABARCODE
Image configuration . . . . . . . . . : *NONE
Destination options . . . . . . . . . : *NONE
Print separator page . . . . . . . . . : *NO
User defined option . . . . . . . . . : *NONE
User defined object:
Object . . . . . . . . . . . . . . . : *NONE
Library . . . . . . . . . . . . . :
Object type . . . . . . . . . . . . :
User driver program . . . . . . . . . : *NONE
Library . . . . . . . . . . . . . . :
Well, that is what I thought as well, but I am not even able to locate what is wrong and where. I am not an AS/400 person :) so I know very little about it.
Thanks for any help!
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Hi SGI_Indy,
I didn't knew that TLBARCODE is a the library for TL Ashford's BarCode/400 product. I don't really goes with 3th party for my Zebras but I agree with Gary. In this case, you should talk to them first.
Let us know what goes on.
Lewis
I didn't knew that TLBARCODE is a the library for TL Ashford's BarCode/400 product. I don't really goes with 3th party for my Zebras but I agree with Gary. In this case, you should talk to them first.
Let us know what goes on.
Lewis
ASKER
I am working with Zebra and TLA on this. Will let you know the result. Thanks for the help so far, but I am sure that this is far from over.
I've done quite a bit of TLA work, so fee free to post back if you cant get it resolved with TLA. Make sure and post your OS/400 version and TLA software version (you can get both from greenscreen menu GO LICPGM, option 10).
- Gary Patterson
- Gary Patterson
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Happy to help.
- Gary Patterson
- Gary Patterson
If your developers have created a custom workstation customization object for this printer, then they may need to make modifications to the workstation customization object, or to the application program that generates the printer-specific language (this printer supports CPLC/EPL/ZPL/EPL2/Extensib
The AS/400 does not provide direct support for any of these languages, as far as I know, so custom code, workstation customization, and/or print driver programs are required.
First you need to determine what printer language is being used, then you need to consult the Technical Reference or Programmer's guide for that printer language (Zebra tech support can help you obtain that - it can be tricky to find them on the Zebra web site), then you need to find the command that sets "gap sensing mode", and substitute the command for the mode you need.
- Gary Patterson