Not quite true. Consider the CR translation, for example. (0x0d <-> 0x25)

"Renkema, Rick" <RenkemaR@xxxxxxxxxxxxxx> wrote:

In ASCII to EBCDIC translation, no value below x'20' is converted.
In EBCDIC to ASCII translation, no value below x'40' is converted.

The only way to be certain, is to try it.

Rick

P Please consider the environment before printing this e-mail

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Vinay Gavankar
Sent: Thursday, 24 February 2011 10:04 AM
To: Midrange Systems Technical Discussion
Subject: Re: QTCPASC table data / Max number of records in physical
file

Thanks Scott.

If QTCPASC is not the default table, what is it? As long as the 2
characters I am interested in are not translated to something
different,
I am a happy camper.

On Wed, Feb 23, 2011 at 6:13 PM, Scott Klement
<midrange-l@xxxxxxxxxxxxxxxx>wrote:

Hello,

comments in-line.

On 2/23/2011 4:48 PM, Vinay Gavankar wrote:
1. How are the hex characters '1C' and '1E' translated when FTPed
to

an ASCII system? I think they remain the same, but want to be
certain. Is
there
a way to look at QTCPASC table data?

You can use WRKTBL QTCPASC, and take option 5 to see the table.

However, by default, FTP does not use QTCPASC. (It should be possible

to change that by specifying TBLFTPOUT/TBLFTPIN when you run the FTP
command.. but I haven't tried it.)


2. What is the current maximum number of records allowed in a
physical
file
member?

4.2 billion records, or 1.8 terabytes. (Per member)
--
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.


***********************************************************************************
The information in this e-mail message and any files transmitted with
it are intended to be confidential and for the use of only the
individual or entity to whom they are addressed. The message and files
may be protected by legal professional privilege, or other legal rules.
The confidentiality of and privilege applying to this message and files
is not waived if this message or files has been sent to you by mistake.
If the reader of this message or files is not the intended recipient,
you are notified that retention, distribution or copying of this
message and files are strictly prohibited. If you receive this message
or files in error, please notify us immediately by telephone or return
e-mail and delete all copies from your computer system. It is the
recipient's responsibility to check this message and files for viruses.
Thank you.
***********************************************************************************

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

--
Sent from my Galaxy tablet phone with with K-9 Mail. Please excuse my brevity.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.