Re: AFPDS conversion to text -- MIDRANGE-L

In the meantime I managed to create ascii files from afpds spooled files. It took some experimenting with the tags, but now it's finally working. If anybody is interested, here is the source code for WSCST object I'm using:

:WSCST DEVCLASS=TRANSFORM.
:TRNSFRMTBL.
:SPACE
DATA ='20'X.
:LINEFEED
DATA ='0A'X.
:VERAMOV
VAROFFSET = 0
VARLEN = 0
VARTYPE = CHRDEC
CNVNUM = 1
CNVDEN = 720
DATA = '0D0A'X.
:EWSCST.

I use IBM supplied command HPTTOFLR (delivered "as is") and the above defined WSCST object to create ASCII files in QDLS.

Thanks,
Goran

--- On Mon, 6/23/08, Goran Saric <goran_saric@xxxxxxxxx> wrote:

From: Goran Saric <goran_saric@xxxxxxxxx>
Subject: Re: AFPDS conversion to text
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Date: Monday, June 23, 2008, 5:50 PM
No, I don't think that the codes need to be in EBCDIC. I
did some tests since my original post and it seems to me
that the linefeed "event" doesn't get
triggered for AFPDS spooled files. I think that Vertical
Absolute Movement (VERAMOV) tag should be used, but I
can't seem to pick the right values for the parameters.
I'm still in the dark with this one...

----- Original Message ----
From: Michael Ryan <michaelrtr@xxxxxxxxx>
To: Midrange Systems Technical Discussion
<midrange-l@xxxxxxxxxxxx>
Sent: Monday, June 23, 2008 8:03:42 PM
Subject: Re: AFPDS conversion to text

Just a WAG, but do the hex codes need to be in EBCDIC since
it's being
converted? Or, is it some other code page problem?

On Mon, Jun 23, 2008 at 12:35 PM, Goran Saric
<goran_saric@xxxxxxxxx> wrote:

I'm trying to convert AFPDS spooled files to ASCII

files to get to the raw text data. I'm using the host
print API (QWPZHPTR, QwpzHostPrintTransform), or to be more
specific, I'm using the IBM supplied (as is) utility
HPTTOFLR which is built around the host print API. I have
created my own WSCST object based on the following code:

:WSCST DEVCLASS=TRANSFORM.

:TRNSFRMTBL.
:PRTDTASTRM
DATASTREAM=IBMNONPAGES.
:SPACE
DATA ='20'X.
:CARRTN
DATA ='0D'X.
:FORMFEED
DATA ='0C'X.
:LINEFEED
DATA ='0D0A'X.
:EWSCST.

The problem is in the fact that the resulting text

file doesn't contain carriage return characters at the
end of each line even though they are specified in my
custom WSCST object. All the other characters get converted
correctly. I have tried various different hex characters in
my code, but none of them seems to work.

Any help with this problem is appreciated.

Thanks.

--
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:

http://lists.midrange.com/mailman/listinfo/midrange-l

or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the

archives

at http://archive.midrange.com/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:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/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:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.