× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. February 2011

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.



As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
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.