MyPurge

Enhanced PURGE, supports WHERE clauses for Owner, EOF, and creation time

17Aug2011
File names of local files get the node name stipped.

26Nov2010
The 'where definitions' such as:
- equal ("=")
- smaller ("<")
- differenr ("<>")
etc. can be used without surrounding blanks.
e.g. the command: "MYPURGE *,where code=700" is valid and accepted.

15Oct2010
File errors were displayed to the base of 19 instead of 10.

06Oct2010
Handling of file code and EOF fixed.

04Oct2010
The time handling is fixed: Modifiers like "=" and "<" etc. work OK now.

22Sep2010
Support of ALLAK modifier: When present all file related alternate key files will be purged as well.
e.g. MYPURGE EXEC* ALLAK
directs MyPurge to purge all files matching template EXEC*, and all alternate key files, related to the template matching files.

18Aug2010
Support of CODE-modifyer added.
MyPurge now can be directed to purhe files by their name and file code.
e.g. MYPURGE *.A*A where code = 7377

05Aug2010
User IDs where not processed correctly.
This bug, introduced yesterday, is fixed.

04Aug2010
OSS files are no longer taken into account.

11May2010
Key word CREATIONTIME added.
Allows a purge command like: MYPURGE $GHS1.*.*ZZ*?? where CREATIONTIME > 01Jan2010 12:00

06May2008
Typo in HELP text fixed.

13Oct2005
A confirmation message is now displayed to the interactive user BEFORE the purge action is executed.
Introduction of ! (exclamation mark) in the parameter message: When present, the confirmation message is suppressed.

MYPURGE
purges all files, belonging to a given user.

To successfully purge all files, the MYPURGE user has to have PURGE access
rights on the files.

HP-NonStop Security

Secure your HP-NonStop system with security software and privileged system products and tools from GreenHouse Software & Consulting