Product Affected: MailStream Plus™, Tag Print System II™, all versions
Product Feature: Running a batch script
Operating System: Windows
Product Feature: Running a batch script
Operating System: Windows
Issue
MailStream Plus™ (MSP) job is run through a batch file execution that is set to run through a job scheduling software.
The Tag Print System II was added after the MSP job step. This step is executes the printing of tray tags via a command line in the batch job.
Everything works fine from a MSP processing and tray tag printing perspective, however the tray tag printing hangs the batch job which timeouts and then has to be manually killed.
The mailer asked is this problem has been seen before and if there were any suggestions for resolution?
The Tag Print System II was added after the MSP job step. This step is executes the printing of tray tags via a command line in the batch job.
Everything works fine from a MSP processing and tray tag printing perspective, however the tray tag printing hangs the batch job which timeouts and then has to be manually killed.
The mailer asked is this problem has been seen before and if there were any suggestions for resolution?
Cause
Batch job script looks like this:
…
PUSHD %MSPGRP1%\MSP\lib
wrun32.exe "%MSPGRP1%\MSP\lib\MSDR00.acu"
POPD
REM %MSPGRP1%\MSP\lib\MSDR00
REM IF %ERRORLEVEL% NEQ 0 goto mmError
ECHO MSDR00 ended %G1RC%
Rem ************ Convert execution report files to rich text format
%MSPGRP1%\MSP\lib\RPT2RTF -L %MSPGRP1%\MSP\data\%G1JOB%.RPT %MSPGRP1%\MSP\data\%G1JOB%.RPT.RTF
%MSPGRP1%\MSP\lib\RPT2RTF -L %MSPGRP1%\MSP\data\%G1JOB%.XLG %MSPGRP1%\MSP\data\%G1JOB%.XLG.RTF
TagPrint.exe %MSPGRP1%\MSP\data\%G1JOB%.TRA /p
Rem ----------------------------------------------------------
Rem Finish up
Rem ----------------------------------------------------------
:CLEANUP
…
The MSP step runs fine.
TagPrint.exe run by itself runs fine.
Calling the MSP job and then TagPrint.exe causes jobs to hang.
…
PUSHD %MSPGRP1%\MSP\lib
wrun32.exe "%MSPGRP1%\MSP\lib\MSDR00.acu"
POPD
REM %MSPGRP1%\MSP\lib\MSDR00
REM IF %ERRORLEVEL% NEQ 0 goto mmError
ECHO MSDR00 ended %G1RC%
Rem ************ Convert execution report files to rich text format
%MSPGRP1%\MSP\lib\RPT2RTF -L %MSPGRP1%\MSP\data\%G1JOB%.RPT %MSPGRP1%\MSP\data\%G1JOB%.RPT.RTF
%MSPGRP1%\MSP\lib\RPT2RTF -L %MSPGRP1%\MSP\data\%G1JOB%.XLG %MSPGRP1%\MSP\data\%G1JOB%.XLG.RTF
TagPrint.exe %MSPGRP1%\MSP\data\%G1JOB%.TRA /p
Rem ----------------------------------------------------------
Rem Finish up
Rem ----------------------------------------------------------
:CLEANUP
…
The MSP step runs fine.
TagPrint.exe run by itself runs fine.
Calling the MSP job and then TagPrint.exe causes jobs to hang.
Resolution
UPDATED: May 14, 2019Add :
cmd.exe /c
on the line prior to the tagprint.exe command and it will close the session spawned by the printing, like this:
cmd.exe /c TagPrint.exe %MSPGRP1%\MSP\data\%G1JOB%.TRA /p