Hi John,
I think I understand what you want to do but as you say, it is probably no
so simple as it involves multiple processes.
- The PRTDTMDOC command creates a pooled file (not a pdf) in the output
queue PRTPDFIT and then you program go to the next instruction... the PDF
does not exist at that time...
- the writer associated with the output queue PRTPDFIT is configured to
use transform services and will create asynchronously in another process
the PDF file...
depending of the configuration of the device PRTPDFIT ans the associated
PSF configuration, it is possible to define a dataqueue that will receive
a message when the PDF is created...
So you probably need to create a program tha reads the dataqueue and
rename the stream file... and leave this program active in a batch NEP
job...
you cold possibly read the dataqueu in the same program, but there is no
guarantee that the message that you read is for the spooled file that you
created...
another more simple option could be to not use the PRTPDFIT but just a
standard ouptut queue ..
so in your program use
PRTDDMDOC ... OUTQ(QPRINT)
and after the MONMSG add something like
CPYSPLF FILE(QPRTDTM/or whatever is the name of the print file)
SPLNBR(*LAST)
TOFILE(*TOSTMF)
TOSTMF(&theFileNameyouwant)
WSCST(*PDF)
this must be tested as not evything converts to PDF using CPYSPLF...
KR
Paul
From: John Candidi <jacandidi@xxxxxxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion
<midrange-l@xxxxxxxxxxxxxxxxxx>
Date: 20/03/2019 16:40
Subject: IFS CL Help
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxxxxxxxx>
Thanks to everyone with their previous help. I have decided to print
documents to PDF's, which will be uploaded into a new document processing
application and be displayed as a PDF. The problem is that the name of the
PDF is too long so I need to create a final filename that uniquely
identifies the output so that it can be cross referenced and reattached to
the correct file in the new application. I have created a unique cross
reference field by using the ROW NUMBER () statement in my SQL that
created the output file that I declared here (DTMOUT9). The field name is
newnameobj and I am trying to rename the output file using that field.
When I try to rename the output before printing, I get a message saying
it can't locate the object. Any ideas how I can fit something into this to
do that. I took my rename statement out.
Again I apologize for the "simplicity" of the problem, but appreciate any
help. In the end I want the out filename to be somethin
DCLF FILE(JACQRYLIB/DTMOUT9)
START:
LOOP:
RCVF
MONMSG MSGID(CPF0864) EXEC(GOTO CMDLBL(THEEND))
IF (&TYPEOBJ *NE *STMF) THEN(GOTO CMDLBL(LOOP))
PRTDTMDOC DOC(&NAMEOBJ) DIR(%TRIM(&PATHDIR)) +
DEV(PRTPDFIT) OUTQ(*LIBL/*DEV)
MONMSG MSGID(ERR0350) CMPDTA(*NONE) EXEC(GOTO LOOP)
GOTO LOOP
John A. Candidi | IT Systems, Applications and Support Manager
2250 Chapel Avenue West, Suite 200, Cherry Hill, NJ 08002
[cid:image012.jpg@01D1C259.112E7430]
Office: 856-779-6915
Cell: 484-645-5598
Fax: 856-779-0719
Email: jacandidi@xxxxxxxxxxxxxxxxx<mailto:elselfe@xxxxxxxxxxxxxxxxx>
Web: www.aeiginsurance.com
[cid:image002.png@01D35ED7.4FE40700]<
https://www.facebook.com/AEIGinsurance> [
cid:image003.png@01D35ED7.4FE40700] <
https://www.linkedin.com/company/american-european-insurance-group-inc-/>
[cid:image004.jpg@01D35ED7.4FE40700] <
https://www.twitter.com/aeiginsurance>
Confidentiality Notice: This message and any attachments contain
confidential, proprietary, or privileged information and is intended only
for the intended recipients. If you are not an intended recipient, you
should not disseminate, distribute, or copy this e-mail. Please notify the
sender immediately by e-mail if you have received this e-mail by mistake
and delete this e-mail from your system. E-mail transmission cannot be
guaranteed to be secure or error-free as information could be intercepted,
corrupted, lost, destroyed, arrive late, or incomplete, or contain
viruses. The sender therefore does not accept liability for any errors or
omissions in the contents of this message, which arise as a result of
e-mail transmission. If verification is required, please request a
hard-copy version.
midrange.com
