It's all about the answers!

Ask a question

RTC 4.0 - ISPF gateway - /var/ispf/WORKAREA - how does RTC manage the files under WORKAREA


Donald Poulin (2249119107) | asked Jul 25 '12, 5:51 a.m.
edited Jul 25 '12, 12:20 p.m.
RTC uses the ISPF gateway for promotes, package, deploys, etc. - how does RTC handle cleaning up files and folders created under WORKAREA and under what circumstances are files/folders not removed.


Comments
Seth Packham commented Jul 25 '12, 9:58 a.m.
FORUM ADMINISTRATOR / JAZZ DEVELOPER

We require all postings to have a clear, specific QUESTION in the title field. Please edit this right away to rephrase the title as a proper question. It will yield more responses.

One answer



permanent link
Guy Slade (64158) | answered Jul 26 '12, 10:25 a.m.
JAZZ DEVELOPER
The ISPF gateway decides how to use and what to put in its work area ... not RTC. Here is what we do know (thanks to Liam's expertise) but it may not be the complete story...

When a build is running there are 2 files created in this directory for the user, for example:

DOHERTL.last
DOHERTL.ID082263.ISPF.SYSTSPRT

Per invocation of the gateway there is one SYSTSPRT file created that is deleted when the process is done. The .last file is kept I suspect for the purposes of debug. If you get a problem you will at least have the last gateway log. If you wanted these to be deleted then you would need to raise an RFE against the ISPF team.

The only reason the SYSTSPRT data set would be left behind would be a) in the event of an abend or b) If the ISPF gateway could not delete it because it was in use (Maybe the user is browsing it).

In addition, if you are running the ISPF Gateway in reusable session mode the user will have a new directory created with a name of their userid. In this directory will be the files required to remember session information. namely:

spawn.wait, ISPFPID.cmd, ISPFPID.log, ISPFPID.log_init, ISPFPID.log_session_last, ISPFPID.561, ISPZCMD.pidlog      

Your answer


Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.