The following command line options are available in standard APPX, whether running APPX from Unix or from Windows/NT:
-k define a new keymap
-m=<[user_id:]keymap_name> override keymap ID
-d=<database_id> override startup database
-a=<application_id> override startup application
-t=<process_type> override startup process type
-p=<process_name> override startup process name
-i=<flat_file_name> convert a flat file into APPXIO format
-e=<data_file_name> convert an APPXIO file into a flat
format
-v=<data_file_name> verify the integrity of an APPXIO file
-an=<data_file_name> analyze an APPXIO file
-l=<log_file_name> start a license server
Invoking in Unix
In Unix, invoke command line options by running APPX with the following command structure:
appx –(x)
where (x) is the option of choice.
Invoking in Windows
In Windows, invoke command line options by running APPX with the following command structure:
appxutil.exe –(x)
where (x) is the option of choice.
Restrictions
An application_id and process_type must always be included when specifying a process_name. If an application_id is included without specifying a process_type/name, the startup menu for the application is used.
If no application_id is specified, the startup application and menu for the database is used. If no database_id is specified, the startup database defined for the user within System Administration is used. If the startup database is also unspecified, the APPX main menu is used.
The valid process_types are Menu, Job, Input, Output, Update, Action, Inquiry, Query, Status, and Subroutine. Use underscores (_) in place of any embedded spaces within parameters.
Option Detail
Option detail is provided as needed for some command line options below:
-k
Invokes the keyboard mapper to either replace an existing keyboard map or to define a new keyboard map. The keymap will be stored by Terminal Type and APPX User ID so that you only have to define a desired map once for each terminal you will be using. Note that if you run APPX using the APPX Client, the keymap is hard-coded and may not be changed.
-m=[user_id:]keymap_name
Overrides the default name for this keymap. For example, if you are using a vt320 terminal your map will be called vt320 by default. This option is particularly useful if, for example, you have a laptop computer that has a software package to emulate a vt320 terminal and you dial in to your system remotely. Although the terminal setting will appear the same to the system, you can define a different keyboard map (called perhaps "laptop") to use when you log in remotely.
-i=filename
Converts an APPX flat ASCII portable file into an APPXIO format portable file. APPX portable files must be converted to and from flat ASCII format when moving between systems of different byte ordering.
-e=filename
Converts an APPXIO format portable file into an APPX flat ASCII portable file. APPX portable files must be converted to and from flat ASCII format when moving between systems of different byte ordering.
-v=filename
Checks the integrity of an APPXIO format file. "filename" specifies the file to be analyzed. This does the same thing as interactive “Verify Files Menu", "Verify Integrity" from the Database, Design File, and System Administration File Management menus, but from a command line.
If the invocation of this command results in no output, then the file passes verification. Any output from this command means that the file fails verification.
-an=filename
Performs an interactive analysis of an APPXIO format file. "filename" specifies the file to be analyzed. Type "help" at the prompt to get a list of valid analysis commands. Valid commands are:
verify key #all counts the number of records in the .dat portion of the file, verifying the data as it goes, and verifies all keys in the .key portion of the file.
help lists all available commands.
dump header gives you information about the file, including the number of keys.
count rec gives you a count of the number of records that filename.dat believes it contains.
verify key #0 verifies the primary index, and gives you the number of records.
verify key #1 verifies the first alternate index, and gives you the number of records.
verify key #2 verifies the second alternate index, and gives you the number of records. You can continue on this way until all index files are verified.
quit exits the "-an=" utility.
verify freelist gives you an error message if the file’s freelist is damaged. The freelist is the list of pointers in APPXIO files that point to deleted records. If this list gets damaged, it may point to a live record, indicating erroneously that it is deleted. verify key #all does not detect damaged freelists. If you get an error message from the verify freelist command, run verify key #all; if no errors occur, you can safely export and re-import the data to initialize the freelist.
If the file does not pass #all verification, but does pass count rec verification, it means that the *.dat portion of the file is probably undamaged, but the *.key indices are probably damaged. In this case, rename or delete the *.key file, then run Create Files in Database Management. This will recreate your indices from scratch. Then, if the freelist was damaged, you can safely export and re-import the data to initialize the freelist.
If the file does not pass count rec analysis, you have a seriously damaged *.dat file. At this point you should either run the ‘recover.exe’ procedure, or if necessary restore the file from a backup.