×

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.




Have you thought about storing the source members with all the date and sequence fields in SVN ?

Then when you pump them to the 400 the line numbers would get maintained.

Regards,


Richard Schoen
Director of Document Management
e. richard.schoen@xxxxxxxxxxxxxxx
p. 952.486.6802
w. helpsystems.com

----------------------------------------------------------------------

message: 1
date: Wed, 22 Nov 2017 11:19:57 -0700
from: Charles Wilt <charles.wilt@xxxxxxxxx>
subject: Re: FTP into Source PF...anyway to control the Sequence#?

Thanks Matt!

That will help.

Charles

On Wed, Nov 22, 2017 at 10:47 AM, Tyler, Matt <matt.tyler@xxxxxxxxxxxxxx>
wrote:

RGZPFM with SRCOPT()
*SEQNBR
The records have a new sequence number placed into the
sequence number field. The SRCSEQ parameter specifies
a start value and a value to be added.

-Matt


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Charles Wilt
Sent: Wednesday, November 22, 2017 10:45 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: FTP into Source PF...anyway to control the Sequence#?

All,

We FTP source members from an SVN working copy on our PC to a IBM i
PF_SRC file.

The problem we've run into is we've got a few huge programs, which end
up with a seq# of 9999.00 repeated for hundreds or thousands of lines
at the end of the program.

They compile fine, but if we happen to need to debug one of them,
using the *LIST debug view...the debugger freaks out.

Failing that....anybody know of an existing command line tool that
will re-sequence a source member in place?

Thanks!
Charles
--


As an Amazon Associate we earn from qualifying purchases.

This thread ...


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

This mailing list archive is Copyright 1997-2026 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.