3 ms·
This was one of the neatest features of the computer formerly known as AS/400: each job (batch or interactive) had its own temporary library (QTEMP). You could
by ASalazarMX 8y ago
This was one of the neatest features of the computer formerly known as AS/400: each job (batch or interactive) had its own temporary library (QTEMP). You could create objects there knowing only you could see them, and the library was destroyed the moment the job ended. Definitely will try polyinstantiated directories.
- gerdesj 8y agoWhat do you mean former? There is an AS/400 in our data centre that we look after for a customer for their off site DR box, with constant DB replication. It is about four years old, the platform is rather older. Bloody noisy beast especially on boot up (IPL?) sounds like a helicopter winding up. It was switched on after racking and that was it - I'm told it is simply available.
- schoen 8y agoAlthough the platform still exists, IBM has renamed it: https://en.wikipedia.org/wiki/IBM_System_i https://en.wikipedia.org/wiki/IBM_System_i
- ASalazarMX 8y agoA bland attempt at humor. They've had more name changes than the artist formerly known as Prince (AS/400, eServer iSeries, System i).
- walterbell 8y agoWindows Sandbox will have this, the app runs in a disposable VM using copy-on-write memory.
- viraptor 8y agoLike the repo mentions - this is just one switch away in systemd. But even without it, you can achieve this with namespaces and mounts.