|
data
Rob,
Not sure what you mean "there is no way that will make a
"real" pdf file".
My example of CPYTOSTMF does create a real pdf file
(of course there is additional code that writes the pdf
into the file XFWPDF). I did not include the complete CLreal
program code only cut and paste the CPYTOSTMF from my
joblog.
My cl program works on many different machines creating
pdf files.without
However, the problem I am encountering is only occuring on
the machine in Japan.
I searched IBM site and googled and yahooed CPFA0DB
finding any useful information on possible causes.command
I could add - I am able to use Windows Explorer to find
files in my library by drilling down through directory
QSYS.LIB
John
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
rob@xxxxxxxxx
Sent: Wednesday, June 06, 2007 8:43 AM
To: Midrange Systems Technical Discussion
Subject: Re: CPFA0DB when using CPYTOSTMF
On a tangent, there is NO way that will make a "real" pdf
file.
Hopefully what you sent was an exact copy/paste. The only
hits I found at
IBM's site had to do with their internal use of the
and forgettingFROMMBR('/qsys.lib/rob.lib/jallen.file/jallen.mbr'
the leading slash in front of qsys.lib.
crtpf rob/jallen rcdlen(10)
upddta rob/jallen
CPYTOSTMF
)the
TOSTMF('/rob/TestFile.PDF')
STMFOPT(*REPLACE)
STMFCODPAG(*PCASCII)
CPCA082-Object copied.
CRTDUPOBJ OBJ(JALLEN) FROMLIB(ROB) OBJTYPE(*FILE)
TOLIB(QTEMP) DATA(*YES)
Object JALLEN in QTEMP type *FILE created.
1 objects duplicated.
CPYTOSTMF
FROMMBR('/qsys.lib/qtemp.lib/jallen.file/jallen.mbr')
TOSTMF('/
rob/TestFile2.PDF') STMFOPT(*REPLACE) STMFCODPAG(*PCASCII)
Object copied.
v5r4
WRKPTFGRP
PTF Group Level
SF99540 7107
SF99539 45
SF99504 10
SF99348 2
SF99347 7
SF99323 11
SF99321 1
SF99318 7
SF99317 7
SF99316 3
SF99315 6
SF99312 15
SF99311 8
SF99309 8
SF99308 8
SF99306 3
SF99304 3
SF99296 5
SF99291 7
SF99186 12
SF99143 1
SF99114 9
Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
"John" <jallen@xxxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
06/05/2007 05:12 PM
Please respond to
Midrange Systems Technical Discussion
<midrange-l@xxxxxxxxxxxx>
To
<MIDRANGE-L@xxxxxxxxxxxx>
cc
Fax to
Subject
CPFA0DB when using CPYTOSTMF
I have done this many times on other machines but for some
reason whenever I execute the
following CPYTOSTMF on this particular machine (V5R4) I am
getting CPFA0DB
CPYTOSTMF
FROMMBR('/qsys.lib/qtemp.lib/XFWPDF.file/XFWPDF.mbr')
TOSTMF('/DRC/USR01/TestFile.PDF') STMFOPT(*REPLACE)
STMFCODPAG(*PCASCII)
(Note: This file and member does exist in QTEMP, and the
directory /DRC/USR01 does exist and I have all authorities
to it)
Message text for CPFA0DB is not real helpful:
Message . . . . : Object name not a QSYS object.
Cause . . . . . : The operation expected an object in
QSYS file system.QSYS.LIB.
Object &1 does not result in an object in the QSYS file
system. Possible
causes:
--The object is in a different file system.
--The object name does not start at the root file
system.
--The first component of the path name is not
but
--The object is on a remote file system.
Recovery . . . : Determine the correct name for the
object. Only local
QSYS file system objects are valid for this operation.
Retry the operation.
Can someone point me to where/what I should be looking to
find the cause of this error?
This machine is in Japan and I am accessing it remotely
I cannot figure out why that would cause this particularthe
error.
I have seen many errors in regards to Code page problems
using a machine in Japan, But that does not appear to be
cause of this error.http://lists.midrange.com/mailman/listinfo/midrange-l
Any guidance would be greatly appreciated
John
--
This is the Midrange Systems Technical Discussion
(MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
or email: MIDRANGE-L-request@xxxxxxxxxxxxarchives
Before posting, please take a moment to review the
at http://archive.midrange.com/midrange-l.http://lists.midrange.com/mailman/listinfo/midrange-l
--
This is the Midrange Systems Technical Discussion
(MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
or email: MIDRANGE-L-request@xxxxxxxxxxxxarchives
Before posting, please take a moment to review the
at http://archive.midrange.com/midrange-l.(MIDRANGE-L) mailing list
--
This is the Midrange Systems Technical Discussion
To post a message email: MIDRANGE-L@xxxxxxxxxxxxhttp://lists.midrange.com/mailman/listinfo/midrange-l
To subscribe, unsubscribe, or change list options,
visit:
or email: MIDRANGE-L-request@xxxxxxxxxxxxarchives
Before posting, please take a moment to review the
at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.