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



Why do you not like sequence numbers? When there is a problem in the code, isn't it nice to have the system tell you where it is? It's not like RDI make syou look at them.

-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Ken Killian
Sent: Thursday, September 03, 2015 7:37 AM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries <wdsci-l@xxxxxxxxxxxx>
Subject: Re: [WDSCI-L] RDi 9.5 announcement

Vern,

Let's hope they finally rid of the Sequence numbers from the old Univac punch-card days. I guess the fossil would drop their punch cards, and need the sequence number to resort their dropped cards. According to a history of our forefathers. <smirk>

Gee, email, documents, my tablets do NOT have 80-column limits. Nor do they have antiquated punch-card sequence numbers.

PS. Use RDI, where you can save a tree, and use the "back-space" button for a typo. No need waste a tree on punch cards! <ROLMA>

-Ken Killian-

-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Vernon Hamberg
Sent: Wednesday, September 02, 2015 6:08 PM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries
Subject: Re: [WDSCI-L] RDi 9.5 announcement

Even today SEU (I had said PDM) will not edit a source PF with record length > 252 - never has been able to. We've been able to specify a length up to 32,766 since at least V3R2 - that's the oldest CL reference I have access to.

So this length thing isn't the nail - just the built-in issues when you deal with syntax checking of things no longer understood by SEU.

Cheers
Vern

On 9/2/2015 4:01 PM, Sam_L wrote:

Did you mean SEU has a limit of 240 chars. I wonder if increasing the
record length will mean that SEU will no longer be able to edit such
source files, regardless of syntax checking. Another nail in the SEU
coffin? Interesting...

Sam

On 9/2/2015 7:27 AM, Vernon Hamberg wrote:
To reply further to Justin on the record length - length of 112 means
there are 100 characters available - but only positions 8-80 are
available for code - 81-100 are for comments.

A source file with 80-character data is actually 92 long, the default.

PDM has a limit of 240 characters that it can process, which is a
record length of 252. CTRSRCPF allows record lengths up to 32,766
which CAN be edited in RDi and for the full length in the new regime.
Before the change upcoming, even with a longer record, only positions
8-80 could be used for code.

Good things happening!!
Vern





--
This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at http://archive.midrange.com/wdsci-l.
--
This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at http://archive.midrange.com/wdsci-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.