Regards,

Martin Gilbert.

What you call a session is a JOB. If you signon multiple times you are running multiple JOBS. Each job has a unique JOB NUMBER. QTEMP is unique per JOB.

Regards,

Martin Gilbert.

When you sign on you start a session, which therefore has its own library QTEMP created and attached to it. This specific library is only visible (fx DSPLIB QTEMP) within this session. As you may understand – QTEMP is a ‘personal’ thing as long as your session is active (= until signoff).

If you run two interactive programs A and B, A may create a file in QTEMP which program B may use when run afterwards from the same session. QTEMP will be deleted with its content when you signoff the session. If you run three sessions (= 3 signon’s) you will have 3 QTEMP libraries all available only to the session that caused their existance.

A submitted job to batch (submitted from anywhere (SBMJOB, JOB-scheduler, jobq or other sources) will also get its own QTEMP, which is only (as in the interative environment described above) available to this spectacular session; – it is therefor NOT possible for anybody to look into it or use its content.

QTEMP is often used to make workfiles avaliable for use by programs run one after the other.
As QTEMP is deleted when the session ends (= you sign off), there is no need for any ‘clean up’.

Every job you start has it’s own QTEMP library. Every interactive login and SBMJOB executed results in it’s own job, and therefore, it’s own QTEMP. For example, if you log on to 2 different 5250 screens, you have two separate QTEMP libraries defined.