Re: FTP into Source PF...anyway to control the Sequence#?

[Charles Wilt <charles.wilt@xxxxxxxxx>]

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
> --
> 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: https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.
> midrange.com_mailman_listinfo_midrange-2Dl&d=DwICAg&c=2S-2xx8Cum_thMfWs-
> kOOHQTwolPvSZ4PFLhr1wDDGs&r=wgq2KO1Tl8HswJht2RKpmz7qvL2YDU
> _M-VhnRH6r43I&m=aFOrvtsM_jxrruhQawEcu6gnt8mE7J0c_
> t0hA3JGQDo&s=6RI9_yNN_zo_UMN4_blFU7si3JnVhZ6QHB1a1Yxx6CE&e=
> or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
> moment to review the archives at https://urldefense.proofpoint.
> com/v2/url?u=https-3A__archive.midrange.com_midrange-
> 2Dl&d=DwICAg&c=2S-2xx8Cum_thMfWs-kOOHQTwolPvSZ4PFLhr1wDDGs&r=
> wgq2KO1Tl8HswJht2RKpmz7qvL2YDU_M-VhnRH6r43I&m=aFOrvtsM_
> jxrruhQawEcu6gnt8mE7J0c_t0hA3JGQDo&s=uT3hO_ENLu7eUxQtzG7JIZkxfr3wQiMu99Qv
> PaePiRc&e=.
>
> Please contact support@xxxxxxxxxxxx for any subscription related
> questions.
>
> Help support midrange.com by shopping at amazon.com with our affiliate
> link: https://urldefense.proofpoint.com/v2/url?u=http-3A__amzn.to_
> 2dEadiD&d=DwICAg&c=2S-2xx8Cum_thMfWs-kOOHQTwolPvSZ4PFLhr1wDDGs&r=
> wgq2KO1Tl8HswJht2RKpmz7qvL2YDU_M-VhnRH6r43I&m=aFOrvtsM_
> jxrruhQawEcu6gnt8mE7J0c_t0hA3JGQDo&s=A90TuxWXkYZhz-
> ykUw6XhoxOWhq3ZbnoXTfBr3jsBcM&e=
>
> --
> 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: https://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxx for any subscription related
> questions.
>
> Help support midrange.com by shopping at amazon.com with our affiliate
> link: http://amzn.to/2dEadiD