Re: COBOL400-L Digest, Vol 10, Issue 27

["Stone, Joel" <Joel.Stone@xxxxxxxxxx>]

Im confused:

I am calling data scrubbing routines Zillions of times (one for each field in millions of records) in OPM.

I thought that a big reason to move to ILE was to improve performance of CALLing separate modules and binding them together.

This should reduce the overhead of the 2nd thru Nth call to the same routine.

But you are stating that OPM is pseudo-doing this time-reduction-efficiency of CALLs anyways??

So - if I break these into modules and bind them a certain way in ILE - the time reduction will be negligible??




-----Original Message-----
From: cobol400-l-bounces@xxxxxxxxxxxx [mailto:cobol400-l-bounces@xxxxxxxxxxxx] On Behalf Of Jon Paris
Sent: Wednesday, October 03, 2012 3:03 PM
To: COBOL Programming on the iSeries/AS400
Subject: Re: [COBOL400-L] COBOL400-L Digest, Vol 10, Issue 27

No - But I hope there is something between END and move or the move only happens at EOF <g>

No - it would be the same - under the covers it just generates a bulk move.

so - assuming that the file stays open that only leaves us with the COBOL logic as a slow-down point.


On 2012-10-03, at 2:22 PM, Stone, Joel wrote:

> OK but ...
>
> I am reading a journal image in from a DSPJRN *OUTFILE
>
> READ JRNFL
> 	
> After the read the user data is chunked into JOESD field which I move to my record format CUST-RECORD so I can access individual fields (or is it columns these days:).
>
> So the next stmt after the read is 
>
> AT END move JOESD to CUST-RECORD
>
> That cant be any more or less efficient than
>
> READ JRNFL into CUST-RECORD
>
> Can it???
>
>
> Thanks!
>
>
>
>
>
> -----Original Message-----
> From: cobol400-l-bounces@xxxxxxxxxxxx [mailto:cobol400-l-bounces@xxxxxxxxxxxx] On Behalf Of Jon Paris
> Sent: Wednesday, October 03, 2012 1:18 PM
> To: COBOL Programming on the iSeries/AS400
> Subject: Re: [COBOL400-L] COBOL400-L Digest, Vol 10, Issue 27
>
> Correct - they apply to both.
>
> You will get a marginal speed improvement by using a bound call but unless millions of calls are involved it would not be a huge saving. 
>
> Make sure your READ statements aren't doing a Read INTO without a good reason for doing so. A lot of programmers do it out of habit. It won't make a huge difference but since COBOL (unlike RPG) maps its FD directly to the buffer it is much more efficient to just use the FD mapped fields than to use INTO to WS.
>
>
> COBOL is a rather "blunt" weapon for string handling with lots of opportunity for inefficient code.  
> On 2012-10-03, at 2:10 PM, Stone, Joel wrote:
>
> > Are your comments for OPM also?  If yes, then ILE probably wouldn't speed things up over OPM right?
> >
> >
> > "However, on subsequent calls, the 
> > system retains a pointer to the routine.  Hence, repeated calls (after the 
> > first one) are now effectively bound to the calling program.  "
> >
> > -----Original Message-----
> > From: cobol400-l-bounces@xxxxxxxxxxxx [mailto:cobol400-l-bounces@xxxxxxxxxxxx] On Behalf Of MichaelQuigley@xxxxxxxxxx
> > Sent: Wednesday, October 03, 2012 11:02 AM
> > To: cobol400-l@xxxxxxxxxxxx
> > Subject: Re: [COBOL400-L] COBOL400-L Digest, Vol 10, Issue 27
> >
> > The biggest advantage I know of for a final call closing files is that you 
> > can later use the same program in a series of other calls.  i.e., Should 
> > the need arise, you can take this program and call it from a command line 
> > (perhaps for debugging purposes, etc.) or you can call it in a series of 
> > programs and know your resources won't be tied up.
> >
> > Regarding statically binding the calls by converting to ILE.  I would have 
> > to agree with Mark.  That's never a bad concept on itself.  But a lot of 
> > things need to be checked.
> >
> > I would like to point out one thing about program calls.  The first time a 
> > dynamic call is made, the program has to resolve the location of the 
> > program object and code to be executed.  However, on subsequent calls, the 
> > system retains a pointer to the routine.  Hence, repeated calls (after the 
> > first one) are now effectively bound to the calling program.  This binding 
> > remains in effect until the run unit ends.  It's been too long, but I 
> > think you can also break the binding by using a CANCEL statement.
> >
> >
> > cobol400-l-bounces@xxxxxxxxxxxx wrote on 10/03/2012 10:54:16 AM:
> >
> > > ----- Message from "Stone, Joel" <Joel.Stone@xxxxxxxxxx> on Wed, 3 
> > > Oct 2012 14:53:39 +0000 -----
> > >
> > > To:
> > >
> > > "'COBOL Programming on the iSeries/AS400'" <cobol400-l@xxxxxxxxxxxx>
> > >
> > > Subject:
> > >
> > > Re: [COBOL400-L] COBOL ILE primer
> > >
> > > Btw, what is the proper way to do this?
> > >
> > > Can I simply open the files once using a first-time-thru flag, and 
> > > then never close the files?
> > >
> > > Or is it better to come thru one last time to close the files?
> > >
> > >
> > >
> > > -----Original Message-----
> > > From: cobol400-l-bounces@xxxxxxxxxxxx [mailto:cobol400-l-
> > > bounces@xxxxxxxxxxxx] On Behalf Of Stone, Joel
> > > Sent: Wednesday, October 03, 2012 9:47 AM
> > > To: 'COBOL Programming on the iSeries/AS400'
> > > Subject: Re: [COBOL400-L] COBOL ILE primer
> > >
> > > This helped - I had done this on one of the called pgms but another 
> > > was opening the same file every time.  This did speed things up 
> > dramatically!
> > > Thanks!!
> > -- 
> > This is the COBOL Programming on the iSeries/AS400 (COBOL400-L) mailing list
> > To post a message email: COBOL400-L@xxxxxxxxxxxx
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/mailman/listinfo/cobol400-l
> > or email: COBOL400-L-request@xxxxxxxxxxxx
> > Before posting, please take a moment to review the archives
> > at http://archive.midrange.com/cobol400-l.
> >
> >
> > ________________________________________________________________________
> > This inbound email has been scanned for all viruses by the MessageLabs SkyScan
> > service. 
> > ________________________________________________________________________
> >
> > ______________________________________________________________________
> > This outbound email has been scanned for all viruses by the MessageLabs Skyscan service.
> > For more information please visit http://www.symanteccloud.com
> > ______________________________________________________________________
> > -- 
> > This is the COBOL Programming on the iSeries/AS400 (COBOL400-L) mailing list
> > To post a message email: COBOL400-L@xxxxxxxxxxxx
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/mailman/listinfo/cobol400-l
> > or email: COBOL400-L-request@xxxxxxxxxxxx
> > Before posting, please take a moment to review the archives
> > at http://archive.midrange.com/cobol400-l.
>
> Jon Paris
>
> www.partner400.com
> www.SystemiDeveloper.com
>
>
>
>
> -- 
> This is the COBOL Programming on the iSeries/AS400 (COBOL400-L) mailing list
> To post a message email: COBOL400-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/cobol400-l
> or email: COBOL400-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/cobol400-l.
>
>
> ________________________________________________________________________
> This inbound email has been scanned for all viruses by the MessageLabs SkyScan
> service. 
> ________________________________________________________________________
>
> ______________________________________________________________________
> This outbound email has been scanned for all viruses by the MessageLabs Skyscan service.
> For more information please visit http://www.symanteccloud.com
> ______________________________________________________________________
> -- 
> This is the COBOL Programming on the iSeries/AS400 (COBOL400-L) mailing list
> To post a message email: COBOL400-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/cobol400-l
> or email: COBOL400-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/cobol400-l.

Jon Paris

www.partner400.com
www.SystemiDeveloper.com