Michael Houser
asked on
duplicate job printed on printer
The users at our warehouse are telling me that when they print a "pick ticket" they get duplicates of some but not others. in the dspmsq qsysopr I can see the duplicate job number
Writer 541275/QSPLJOB/SHIP2F started.
Writer 541275/QSPLJOB/SHIP2F ended normally.
---JOB STARTS---
Message ID . . . . . . : CPF3382 Severity . . . . . . . : 00
Date sent . . . . . . : 08/09/17 Time sent . . . . . . : 05:32:28
Message type . . . . . : Information
From . . . . . . . . . : QSPLJOB CCSID . . . . . . . . : 65535
From job . . . . . . . . . . . : SHIP2F
User . . . . . . . . . . . . : QSPLJOB
Number . . . . . . . . . . . : 541275
From program . . . . . . . . . : QSPWTRM1
To message queue . . . . . . . : QSYSOPR
Library . . . . . . . . . . : QSYS
Time sent . . . . . . . . . . : 05:32:28.188074
---JOB ENDS---
Message ID . . . . . . : CPF3390 Severity . . . . . . . : 00
Date sent . . . . . . : 08/09/17 Time sent . . . . . . : 05:35:13
Message type . . . . . : Information
From . . . . . . . . . : QSPLJOB CCSID . . . . . . . . : 65535
From job . . . . . . . . . . . : SHIP2F
User . . . . . . . . . . . . : QSPLJOB
Number . . . . . . . . . . . : 541275
From program . . . . . . . . . : QSPTRMRW
To message queue . . . . . . . : QSYSOPR
Library . . . . . . . . . . : QSYS
Time sent . . . . . . . . . . : 05:35:13.916036
Time zone abbreviated name . : CDT
This ending and starting I think is what is causing the jobs to be duplicated. All this starting and ending it seems is done all on its own ( I know sounds strange, right?) with not manual intervention. I have tried to test this using the exact same model printer set up on the 400 the exact same way but moving the print jobs and taking an option 6 in its outq to no avail. I have also done a wrkjob on the printer but not sure what I am looking at or for. In the wrkjob I see:
Entered
Option Job User Number Type -----Status----- System
SHIP2F QSPLJOB 542554 WTR ACTIVE 08/09/17
SHIP2F QSPLJOB 542512 WTR OUTQ 08/09/17
SHIP2F QSPLJOB 542243 WTR OUTQ 08/09/17
SHIP2F QSPLJOB 541286 WTR OUTQ 08/09/17
SHIP2F QSPLJOB 541275 WTR OUTQ 08/09/17
SHIP2F QSPLJOB 537492 WTR OUTQ 08/08/17
SHIP2F QSPLJOB 537481 WTR OUTQ 08/08/17
SHIP2F QSPLJOB 537480 WTR OUTQ 08/08/17
SHIP2F QSPLJOB 537464 WTR OUTQ 08/08/17
SHIP2F QSPLJOB 537442 WTR OUTQ 08/08/17
But I don't see any duplicate job numbers..
While looking at the 1st OUQ record I do see this below:
--JOB START--
Job Log S215752W 08/09/17 05:32:25
SHIP2F User . . . . . . : QSPLJOB Number . . . . . . . . . .
QSPLPRTW Library . . . . . : QGPL
SEV DATE TIME FROM PGM LIBRARY INST TO PGM
00 08/08/17 05:54:34.118279 QWTPIIPP QSYS 04C9 *EXT
Message . . . . : Job 537492/QSPLJOB/SHIP2F started on 08/08/17 at 05:54:
in subsystem QSPL in QSYS. Job entered system on 08/08/17 at 05:54:34.
08/08/17 05:54:34.118836 QWTSCSBJ *N QCMD
From user . . . . . . . . . : SHIP2
--JOB END--
00 08/09/17 05:32:25.114368 QWTMCEOJ QSYS 0162 *EXT
Message . . . . : Job 537492/QSPLJOB/SHIP2F ended on 08/09/17 at 05:32:25
1.144 seconds used; end code 50 .
Cause . . . . . : Job 537492/QSPLJOB/SHIP2F completed on 08/09/17 at
05:32:25 after it used 1.144 seconds processing unit time. The maximum
temporary storage used was 8 megabytes. The job had ending code 50. The j
ended after 1 routing steps with a secondary ending code of 0. The job
ending codes and their meanings are as follows: 0 - The job completed
Thanks
Writer 541275/QSPLJOB/SHIP2F started.
Writer 541275/QSPLJOB/SHIP2F ended normally.
---JOB STARTS---
Message ID . . . . . . : CPF3382 Severity . . . . . . . : 00
Date sent . . . . . . : 08/09/17 Time sent . . . . . . : 05:32:28
Message type . . . . . : Information
From . . . . . . . . . : QSPLJOB CCSID . . . . . . . . : 65535
From job . . . . . . . . . . . : SHIP2F
User . . . . . . . . . . . . : QSPLJOB
Number . . . . . . . . . . . : 541275
From program . . . . . . . . . : QSPWTRM1
To message queue . . . . . . . : QSYSOPR
Library . . . . . . . . . . : QSYS
Time sent . . . . . . . . . . : 05:32:28.188074
---JOB ENDS---
Message ID . . . . . . : CPF3390 Severity . . . . . . . : 00
Date sent . . . . . . : 08/09/17 Time sent . . . . . . : 05:35:13
Message type . . . . . : Information
From . . . . . . . . . : QSPLJOB CCSID . . . . . . . . : 65535
From job . . . . . . . . . . . : SHIP2F
User . . . . . . . . . . . . : QSPLJOB
Number . . . . . . . . . . . : 541275
From program . . . . . . . . . : QSPTRMRW
To message queue . . . . . . . : QSYSOPR
Library . . . . . . . . . . : QSYS
Time sent . . . . . . . . . . : 05:35:13.916036
Time zone abbreviated name . : CDT
This ending and starting I think is what is causing the jobs to be duplicated. All this starting and ending it seems is done all on its own ( I know sounds strange, right?) with not manual intervention. I have tried to test this using the exact same model printer set up on the 400 the exact same way but moving the print jobs and taking an option 6 in its outq to no avail. I have also done a wrkjob on the printer but not sure what I am looking at or for. In the wrkjob I see:
Entered
Option Job User Number Type -----Status----- System
SHIP2F QSPLJOB 542554 WTR ACTIVE 08/09/17
SHIP2F QSPLJOB 542512 WTR OUTQ 08/09/17
SHIP2F QSPLJOB 542243 WTR OUTQ 08/09/17
SHIP2F QSPLJOB 541286 WTR OUTQ 08/09/17
SHIP2F QSPLJOB 541275 WTR OUTQ 08/09/17
SHIP2F QSPLJOB 537492 WTR OUTQ 08/08/17
SHIP2F QSPLJOB 537481 WTR OUTQ 08/08/17
SHIP2F QSPLJOB 537480 WTR OUTQ 08/08/17
SHIP2F QSPLJOB 537464 WTR OUTQ 08/08/17
SHIP2F QSPLJOB 537442 WTR OUTQ 08/08/17
But I don't see any duplicate job numbers..
While looking at the 1st OUQ record I do see this below:
--JOB START--
Job Log S215752W 08/09/17 05:32:25
SHIP2F User . . . . . . : QSPLJOB Number . . . . . . . . . .
QSPLPRTW Library . . . . . : QGPL
SEV DATE TIME FROM PGM LIBRARY INST TO PGM
00 08/08/17 05:54:34.118279 QWTPIIPP QSYS 04C9 *EXT
Message . . . . : Job 537492/QSPLJOB/SHIP2F started on 08/08/17 at 05:54:
in subsystem QSPL in QSYS. Job entered system on 08/08/17 at 05:54:34.
08/08/17 05:54:34.118836 QWTSCSBJ *N QCMD
From user . . . . . . . . . : SHIP2
--JOB END--
00 08/09/17 05:32:25.114368 QWTMCEOJ QSYS 0162 *EXT
Message . . . . : Job 537492/QSPLJOB/SHIP2F ended on 08/09/17 at 05:32:25
1.144 seconds used; end code 50 .
Cause . . . . . : Job 537492/QSPLJOB/SHIP2F completed on 08/09/17 at
05:32:25 after it used 1.144 seconds processing unit time. The maximum
temporary storage used was 8 megabytes. The job had ending code 50. The j
ended after 1 routing steps with a secondary ending code of 0. The job
ending codes and their meanings are as follows: 0 - The job completed
Thanks
ASKER
Gary as always thanks for the reply. From what I know and I was out there this am to check on this issue. No one is turning off the printer or anything like that. Is there a way to see a better joblog then qsysopr or workjob ship2f? From talking to another programmer here the user at the DC runs a CL to "kick off the batch job print run"? Could it be something hardcoded on the CL that tells the job to start and end the writer on the 400?
Below is the job log
5770SS1 V7R2M0 140418 Job Log S215752W 08/10/17 05:47:49 CDT Page 1
Job name . . . . . . . . . . : SHIP2F User . . . . . . : QSPLJOB Number . . . . . . . . . . . : 542554
Job description . . . . . . : QSPLPRTW Library . . . . . : QGPL
MSGID TYPE SEV DATE TIME FROM PGM LIBRARY INST TO PGM LIBRARY INST
CPF1124 Information 00 08/09/17 11:19:53.427374 QWTPIIPP QSYS 04C9 *EXT *N
Message . . . . : Job 542554/QSPLJOB/SHIP2F started on 08/09/17 at 11:19:53
in subsystem QSPL in QSYS. Job entered system on 08/09/17 at 11:19:53.
*NONE Request 08/09/17 11:19:53.427990 QWTSCSBJ *N QCMD QSYS 0195
From user . . . . . . . . . : AMY
Message . . . . : -CALL QSYS/QSPWTRM1
CPA403D Sender copy 99 08/10/17 05:47:02.561782 QSPSNDWM QSYS 01E7 QSPSNDWM QSYS 01E7
Message . . . . : Operator action required on device SHIP2F (C R).
Cause . . . . . : An error was detected on device SHIP2F. Look at the
printer to determine the cause of the problem. Recovery . . . : Do one of
the following and try the request again. Possible choices for replying to
message . . . . . . . . . . . . . . . : C -- Enter C to cancel the writer.
R -- Enter R to continue printing the file after the problem at the printer
has been corrected. Technical description . . . . . . . . : For more
information, see your printer's operator guide.
*NONE Reply 08/10/17 05:47:49.352306 QMHRCVM QSYS 0294 *N *N *N
Message . . . . : C
CPC2191 Completion 00 08/10/17 05:47:49.353801 QLIDLOBJ QSYS 0686 QLICLLIB QSYS 0697
Message . . . . : Object SPLAPISPJL in QTEMP type *USRSPC deleted.
CPC2191 Completion 00 08/10/17 05:47:49.354267 QLIDLOBJ QSYS 0686 QLICLLIB QSYS 0697
Message . . . . : Object PJL_DRVRSP in QTEMP type *USRSPC deleted.
CPF1164 Completion 00 08/10/17 05:47:49.354354 QWTMCEOJ QSYS 0162 *EXT *N
Message . . . . : Job 542554/QSPLJOB/SHIP2F ended on 08/10/17 at 05:47:49;
.975 seconds used; end code 50 .
Cause . . . . . : Job 542554/QSPLJOB/SHIP2F completed on 08/10/17 at
05:47:49 after it used .975 seconds processing unit time. The maximum
temporary storage used was 8 megabytes. The job had ending code 50. The job
ended after 1 routing steps with a secondary ending code of 0. The job
ending codes and their meanings are as follows: 0 - The job completed
normally. 10 - The job completed normally during controlled ending or
controlled subsystem ending. 20 - The job exceeded end severity (ENDSEV job
attribute). 30 - The job ended abnormally. 40 - The job ended before
becoming active. 50 - The job ended while the job was active. 60 - The
subsystem ended abnormally while the job was active. 70 - The system ended
abnormally while the job was active. 80 - The job ended (ENDJOBABN command).
90 - The job was forced to end after the time limit ended (ENDJOBABN
command). Recovery . . . : For more information, see the Work management
topic collection in the Systems management category in the IBM i Information
Center, http://www.ibm.com/systems/i/infocenter/.
Thanks again..
Below is the job log
5770SS1 V7R2M0 140418 Job Log S215752W 08/10/17 05:47:49 CDT Page 1
Job name . . . . . . . . . . : SHIP2F User . . . . . . : QSPLJOB Number . . . . . . . . . . . : 542554
Job description . . . . . . : QSPLPRTW Library . . . . . : QGPL
MSGID TYPE SEV DATE TIME FROM PGM LIBRARY INST TO PGM LIBRARY INST
CPF1124 Information 00 08/09/17 11:19:53.427374 QWTPIIPP QSYS 04C9 *EXT *N
Message . . . . : Job 542554/QSPLJOB/SHIP2F started on 08/09/17 at 11:19:53
in subsystem QSPL in QSYS. Job entered system on 08/09/17 at 11:19:53.
*NONE Request 08/09/17 11:19:53.427990 QWTSCSBJ *N QCMD QSYS 0195
From user . . . . . . . . . : AMY
Message . . . . : -CALL QSYS/QSPWTRM1
CPA403D Sender copy 99 08/10/17 05:47:02.561782 QSPSNDWM QSYS 01E7 QSPSNDWM QSYS 01E7
Message . . . . : Operator action required on device SHIP2F (C R).
Cause . . . . . : An error was detected on device SHIP2F. Look at the
printer to determine the cause of the problem. Recovery . . . : Do one of
the following and try the request again. Possible choices for replying to
message . . . . . . . . . . . . . . . : C -- Enter C to cancel the writer.
R -- Enter R to continue printing the file after the problem at the printer
has been corrected. Technical description . . . . . . . . : For more
information, see your printer's operator guide.
*NONE Reply 08/10/17 05:47:49.352306 QMHRCVM QSYS 0294 *N *N *N
Message . . . . : C
CPC2191 Completion 00 08/10/17 05:47:49.353801 QLIDLOBJ QSYS 0686 QLICLLIB QSYS 0697
Message . . . . : Object SPLAPISPJL in QTEMP type *USRSPC deleted.
CPC2191 Completion 00 08/10/17 05:47:49.354267 QLIDLOBJ QSYS 0686 QLICLLIB QSYS 0697
Message . . . . : Object PJL_DRVRSP in QTEMP type *USRSPC deleted.
CPF1164 Completion 00 08/10/17 05:47:49.354354 QWTMCEOJ QSYS 0162 *EXT *N
Message . . . . : Job 542554/QSPLJOB/SHIP2F ended on 08/10/17 at 05:47:49;
.975 seconds used; end code 50 .
Cause . . . . . : Job 542554/QSPLJOB/SHIP2F completed on 08/10/17 at
05:47:49 after it used .975 seconds processing unit time. The maximum
temporary storage used was 8 megabytes. The job had ending code 50. The job
ended after 1 routing steps with a secondary ending code of 0. The job
ending codes and their meanings are as follows: 0 - The job completed
normally. 10 - The job completed normally during controlled ending or
controlled subsystem ending. 20 - The job exceeded end severity (ENDSEV job
attribute). 30 - The job ended abnormally. 40 - The job ended before
becoming active. 50 - The job ended while the job was active. 60 - The
subsystem ended abnormally while the job was active. 70 - The system ended
abnormally while the job was active. 80 - The job ended (ENDJOBABN command).
90 - The job was forced to end after the time limit ended (ENDJOBABN
command). Recovery . . . : For more information, see the Work management
topic collection in the Systems management category in the IBM i Information
Center, http://www.ibm.com/systems/i/infocenter/.
Thanks again..
There is the answer:
CPA403D Sender copy 99 08/10/17 05:47:02.561782 QSPSNDWM QSYS 01E7 QSPSNDWM QSYS 01E7
Message . . . . : Operator action required on device SHIP2F (C R).
Cause . . . . . : An error was detected on device SHIP2F. Look at the
printer to determine the cause of the problem.
Recovery . . . : Do one of the following and try the request again. Possible choices for replying to
message . . . . . . . . . . . . . . . : C -- Enter C to cancel the writer.
R -- Enter R to continue printing the file after the problem at the printer
has been corrected. Technical description . . . . . . . . : For more
information, see your printer's operator guide.
*NONE Reply 08/10/17 05:47:49.352306 QMHRCVM QSYS 0294 *N *N *N
Message . . . . : C
Something went wrong at the printer (could be as simple as a "load paper" or "paper jam" message, for example). About 2.5 minutes later, someone answered the writer error message on the IBM i with a "C" - for "Cancel", which caused the writer to terminate abnormally.
Generally you would fix the problem at the printer (add paper, fix jam, whatever), then reply "R" to retry the failed print operation. As it is, the document is probably queued up in the printer, the writer gets ended, the printer problem gets fixed,the original document prints, the writer gets restarted, and the document gets printed again, since the writer was ended last time before it was deleted from the queue.
Yes, it is possible that the CL is starting/ending writer.
CPA403D Sender copy 99 08/10/17 05:47:02.561782 QSPSNDWM QSYS 01E7 QSPSNDWM QSYS 01E7
Message . . . . : Operator action required on device SHIP2F (C R).
Cause . . . . . : An error was detected on device SHIP2F. Look at the
printer to determine the cause of the problem.
Recovery . . . : Do one of the following and try the request again. Possible choices for replying to
message . . . . . . . . . . . . . . . : C -- Enter C to cancel the writer.
R -- Enter R to continue printing the file after the problem at the printer
has been corrected. Technical description . . . . . . . . : For more
information, see your printer's operator guide.
*NONE Reply 08/10/17 05:47:49.352306 QMHRCVM QSYS 0294 *N *N *N
Message . . . . : C
Something went wrong at the printer (could be as simple as a "load paper" or "paper jam" message, for example). About 2.5 minutes later, someone answered the writer error message on the IBM i with a "C" - for "Cancel", which caused the writer to terminate abnormally.
Generally you would fix the problem at the printer (add paper, fix jam, whatever), then reply "R" to retry the failed print operation. As it is, the document is probably queued up in the printer, the writer gets ended, the printer problem gets fixed,the original document prints, the writer gets restarted, and the document gets printed again, since the writer was ended last time before it was deleted from the queue.
Yes, it is possible that the CL is starting/ending writer.
ASKER
Gary thanks again for the help. Doing some looking in dspmsg qsysopr and takin an F1 on msg:
riter 584669/QSPLJOB/SHIP2F ended normally. I see it as showing: Message ID . . . . . . : CPF3390 Severity . . . . . . . : 00
Message type . . . . . : Information
Date sent . . . . . . : 08/15/17 Time sent . . . . . . : 05:36:58
In thinking I could just get around this message I did a addrpyle and
Sequence Message Opt Number ID Reply Compare Value
1 CPA3394 G 'NET17004'
2 CPF3390 R 'SHIP2F'
But in doing a bit more reading I see that CPF3390 means
Message ID
CPF3390
Message
Device &4 not available. (C R)
Cause
Your job cannot use device because the device is not powered on or is not communicating.
Recovery
Check the printer device to make sure it is powered on. If it is powered on, then check the cable connections and make sure the printer is communicating. Type C to cancel the request or type R to try the request again.
Technical Desc
Reply Choices
C -- Enter C to cancel the writer.
R -- Enter R to retry using the device.
Severity
99
Message Level
13
Alert Option
*NO
Log Problem
*NO
But the in dspmsg qsysopr the next day I see that the message has been answered by a C and not an R so the write is still restarting itself an duplicating the print job
Thanks again..
riter 584669/QSPLJOB/SHIP2F ended normally. I see it as showing: Message ID . . . . . . : CPF3390 Severity . . . . . . . : 00
Message type . . . . . : Information
Date sent . . . . . . : 08/15/17 Time sent . . . . . . : 05:36:58
In thinking I could just get around this message I did a addrpyle and
Sequence Message Opt Number ID Reply Compare Value
1 CPA3394 G 'NET17004'
2 CPF3390 R 'SHIP2F'
But in doing a bit more reading I see that CPF3390 means
Message ID
CPF3390
Message
Device &4 not available. (C R)
Cause
Your job cannot use device because the device is not powered on or is not communicating.
Recovery
Check the printer device to make sure it is powered on. If it is powered on, then check the cable connections and make sure the printer is communicating. Type C to cancel the request or type R to try the request again.
Technical Desc
Reply Choices
C -- Enter C to cancel the writer.
R -- Enter R to retry using the device.
Severity
99
Message Level
13
Alert Option
*NO
Log Problem
*NO
But the in dspmsg qsysopr the next day I see that the message has been answered by a C and not an R so the write is still restarting itself an duplicating the print job
Thanks again..
CPF3390 generally gets issued if the printer is turned off or has lost connectivity (ethernet cable pulled, for example). I'm not sure, but taking the printer offline using the front panel may cause the same message. Suggestions:
- Check physical connectivity. Maybe you have a bad network cable, jack, switch port, etc. Had a similar type of problem once where the network cable had been run under a chair mat. Over time, the cable was damaged, and when the chair rolled over the cable it caused a communication problem.
- Check printer user actions - monitor closely for CPF3390 on this printer and immediately contact the printer user to ask if they are doing anything to take the printer offline. Maybe they power the printer down (usually unnecessary) when it runs out of paper, or maybe the power cord occasionally gets caught on something and pulled and they have to plug it back in.
This question needs an answer!
Become an EE member today
7 DAY FREE TRIALMembers can start a 7-Day Free trial then enjoy unlimited access to the platform.
View membership options
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
1.144 seconds used; end code 50 .
End code 50 means that the job ended while the writer job was active. Writer job probably crashed due to an error. Need to see the rest of the job log to see the errors.
Communication error with printer, bad print file, someone powered the printer off, etc.