Re: SQLRPGLE CLOSE CURSOR

["Clare Babcock" <cbabcock@xxxxxxxxxxxx>]

This is a multi-part message in MIME format.
--
[ Picked text/plain from multipart/alternative ]

/*RCLRSC - I haven't considered it. How would I do that?  Would I need to*/
/*break my program down into several sub-programs, with each returning a*/
/*result set, then issuing a RCLRSC?*/

Not exactly sure how you might implement this. It was just a thought . I do not 
profess to be a GURU in this regard, however, ther is a blurb on the utility of 
this command on the IBM site.  I copied some of this blurb
there is more though.

I assume that your program is called from another program so when control 
returns to pgm1 you could then call a 3 line CL program to perform the RCLRSC.
Or you could call a CL program from pgm2 that does this.

The Blurb....................
The Reclaim Resources (RCLRSC) command is intended for use by the controlling 
program in an application to free resources that were allocated by programs 
that have finished running and returned control to the controlling program. The 
resources used by these programs can then be used by other programs running on 
the system. Based on the reference level specified by the LVL parameter, this 
command reclaims resources that are scoped to the default activation group. 
This command does not reclaim resources that are scoped to the job or resources 
that are scoped to any activation group other than the default activation 
group. The resources that are reclaimed by this command are

  a.. static storage
  For an original program model (OPM) program, its static storage will be 
reclaimed. For a user state Integrated Language Environment (ILE) program, its 
static storage will be marked so that it will be re-initialized on the next 
call. Static storage is not affected for a service program, a system state ILE 
program, or any ILE program running in an activation group other than the 
default activation group.


  b.. open files of object type *FILE

  c.. user interface manager (UIM) application resources

  d.. Common Programming Interface (CPI) Communications conversations

  e.. hierarchical file systems (HFS) resources

  f.. user-defined communications sessions.
In addition, after distributed data management (DDM) files are closed based on 
the criteria described above, all DDM source system conversations in this job 
that are not currently in use will be ended, regardless of the activation group 
or reference level from which they were started.

The RCLRSC command is not needed to reclaim the files and static storage of 
most programs, such as CL programs that end (return) normally, RPG programs 
that have the last record (LR) indicator set on, and COBOL programs. The RCLRSC 
command should not be used if it might be processed while any COBOL program is 
still active in the application.

For more information on the appropriate use of this command, see the 
documentation associated with the programming language(s) used in the 
application.

Restrictions:

  1.. This command is not threadsafe. This command fails in a job that allows 
multiple threads.

  2.. Do not specify LVL(*CALLER) on this command if it is used in a CL program 
that also uses the Send File (SNDF), Receive File (RCVF), or Send Receive File 
(SNDRCVF) commands. Specifying RCLRSC LVL(*CALLER) in such a program causes 
unpredictable results when the SNDF, RCVF, or SNDRCVF commands are used after 
the program runs.

  3.. Do not specify LVL(*CALLER) on this command if it is issued from a 
command line, as this will result in unpredictable results.

--