10Dec2008, Version 310
Code 100 evaluation is now done using BIND.

11Jan2007, Version 300
Version procedure aligned.

15Feb2006
Enhanced to operate on code 800 files.

Do you know the files on a Tandem system, needed to be licensed?
Do you know, which licensed files do NOT need to be licensed?

Once in a while I stumble into the situation, that someone did a

FUP LICENSE $SYSTEM.SYS*.*

to 'be on the save side'.

It is an awful task to re-introduce the right settings.

So I invested a few days, and invented a small tool, that does all
this for me (and you):

- it displays the actual LICENSE flag situation
= licensed OK
= license needed
= revoke needed (because there is no need for a license)

- it corrects the LICENSE flag situation
= it sets the license flag on those type 100, 700 and 800 executables and
library files, containing PRIV or CALLABLE code:
= it sets the license flag on those SQL files, needing it
= it sets the license flag on file $SYSTEM.SYSnn.SORTPROG
= it resets the license flag from those type 100 and 700
executables, NOT containing PRIV or CALLABLE code.
= changes only those files, where a change is required 

For detail information please read the documentation.

In case you find a bug, please let me know, and I'll fix it.

GreenHouse Software & Consulting
Carl Weber