-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
It can prevent accidentally using objects that were created by another
program and accidentally left in QTEMP. The shop I work in doesn't put
it in the library list either. We have several very long running
jobstreams that call lots of sub-programs, and with changes happening,
sometimes beyond our control and unexpectedly, they do break more often
than we'd like. It not being in the library list doesn't cause any
issues as long as you explicitly reference QTEMP when you want to use
something in there. Other places I've worked have put it at the top of
the library list, and used it as sort of an implicit override. Both ways
work fine as long as you're consistent.
Pete Hall
pbhall@xxxxxxxxxxxxx
James Lampert wrote:
| I think I've seen at least one customer box that was set up in such a
| way that QTEMP is not, by default, in the library list.
|
| Not surprisingly, where I've seen (or suspected) this, it has been in
| the context of problems this has caused.
|
| Can anybody explain why (other than total ignorance of the nature of
| QTEMP) anybody would set up a box to do this?
|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla -
http://enigmail.mozdev.org
iD8DBQFHhqvtpcZsDl8OX6kRAgK4AKCKyd1EFy0S1BCBegUzXMiddp+AiACgotaz
CtnYnU+2QWrG87aA0zVI9vg=
=iLfW
-----END PGP SIGNATURE-----
midrange.com
