Difference between revisions of "QTEMP"
From MidrangeWiki
(reformat some text) |
MrDolomite (talk | contribs) m (fixing wikisyntax typo to use square brackets around category instead of braces) |
||
| Line 8: | Line 8: | ||
Conceptually QTEMP is like 'local variables' in a procedure, no other procedure can access a procedures 'local variables', similarly no other job can access a jobs QTEMP library or objects in the jobs QTEMP library. | Conceptually QTEMP is like 'local variables' in a procedure, no other procedure can access a procedures 'local variables', similarly no other job can access a jobs QTEMP library or objects in the jobs QTEMP library. | ||
| − | |||
The intent is that every job will have a place to store objects needed temporarily - for the duration of that particular job, and no longer. | The intent is that every job will have a place to store objects needed temporarily - for the duration of that particular job, and no longer. | ||
| Line 14: | Line 13: | ||
The job's QTEMP library and all objects in it are deleted when the job ends. | The job's QTEMP library and all objects in it are deleted when the job ends. | ||
| + | ==Categories== | ||
{{stub}} | {{stub}} | ||
| − | + | [[Category:Basics 101]] | |
| − | + | [[Category:Q_libraries]] | |
Revision as of 12:15, 15 May 2008
QTEMP is a library created by OS/400 for each job.
QTEMP is very different from other libraries on the system.
Each job has its own QTEMP, separate from every other jobs QTEMP.
QTEMP information CANNOT be shared between jobs.
Conceptually QTEMP is like 'local variables' in a procedure, no other procedure can access a procedures 'local variables', similarly no other job can access a jobs QTEMP library or objects in the jobs QTEMP library.
The intent is that every job will have a place to store objects needed temporarily - for the duration of that particular job, and no longer.
The job's QTEMP library and all objects in it are deleted when the job ends.
Categories
This article is a stub. You can help by editing it.
