APPX Utility

2005-Jun-02 11:04am

      GOSUB    --- CHECK GUI CLIENT
      IF       --- RETURN CODE        EQ     1
T     *        Running with a GUI client
F     *        Running with a character client
To run a background process (cron job) in UNIX, build a script as follows;

  export APPXPATH=/appx/appx350/data
  export TERM=ibm3151
  su - xxx -c "/appx/appx350/appx -s -d=ddd -a=TRN -t=JOB -p=BATCH_CYCLE" 1>/dev/null 2>/dev/null

The first export command is the APPXPATH directory for your APPX installation.
Example: /appx/appx350/data 

The second export command defines the terminal type.  Example: ibm3151.  Even
thought the process is running in the background, the terminal type must be
defined.

The su command line parameters:

     xxx is the o/s userid of who is running this process
        -c " then the APPX application path
        -s tells APPX to automatically pass through any entry screens
           like sort and disposition that might be encountered.
        -d ddd is the database id of the APPX application
        -a application id
        -t process type, most likely a JOB
        -p the name of your process followed by ".  The underscore maintains
           the space you may have in the APPX process name.
        1> and 2> tells appx to send interactive message to the null device.
           These two parameters are to be included in the su line.  

Of course you would have one script for each process you wanted to run in
background.
      *
      *        Send the file to the client
      *
      SET      --- TEMP 80                    =      /tmp/info.csv
      SET      --- TEMP 132                   =      c:\temp\info.csv
      PASS     --- TEMP 80                    FIELD            SHARE? Y
      PASS     --- TEMP 132                   FIELD            SHARE? Y
      CALL         ,RT_SEND_FILE              RESIDENT? N  END? N  FAIL 0
      *
      *        Run Excel and open the file
      *
      SET      --- TEMP 256                   =      @
      APPEND   --- TEMP 256                   0      "C:\Program Files\Micr
      APPEND   --- TEMP 256                   0      osoft Office\Office\EX
      APPEND   --- TEMP 256                   0      CEL.EXE"
      *
      APPEND   --- TEMP 256                   1      c:\temp\info.csv
      *
      SET      --- LI                         =      256
      PASS     --- TEMP 256                   FIELD            SHARE? Y
      PASS     --- LI                         FIELD            SHARE? Y
      CALL         ,RT_LOAD_URL               RESIDENT? N  END? N  FAIL 0
      *
APPX 4.2

The --- PLAY SOUND command ( audio subroutine ) in ILF will support .wav, .au, and .aiff file formats.  Examples;

      SET      --- TEMP 512                   =      /home/pete/test.wav
      PASS     --- TEMP 512                   FIELD            SHARE? N
      GOSUB    --- PLAY SOUND

      SET      --- TEMP 512                   =      file:///home/pete/test
      APPEND   --- TEMP 512                   0      .wav
      PASS     --- TEMP 512                   FIELD            SHARE? N
      GOSUB    --- PLAY SOUND

      SET      --- TEMP 512                   =      http://www.wavsite.com
      APPEND   --- TEMP 512                   0      /sounds/62369/grail22.
      APPEND   --- TEMP 512                   0      wav
      PASS     --- TEMP 512                   FIELD            SHARE? N
      GOSUB    --- PLAY SOUND
      CHILD ID  Invocation Type  Pre-invocation Open?   
      --------  ---------------- --------------------   
      1ST       Subprocess       No                     
      2ND       Subprocess       Yes - open cached      
      3RD       Subprocess       No                     
      4TH       Related          No                     
      5TH       Subprocess       No                     
      6TH       Subprocess       Yes - open base        

  Process A
          |
       detached
          |
  Process B
          |
       related
          |
  Process C
          |
      subprocess
          |
  Process D
          |
      subprocess
          |
  Process E

  -  readnext position (record number/key value plus key path)
  -  an optional record lock
  -  a record buffer
  -  pointer to cached or base file
                            Input Process Invocation Type
              ------------------------------------------------------------
              | Invocation Type   | SubProcess |  Detached  |   Related  |
              |-------------------|------------|------------|------------|
              |                   |            |            |            |
              | SubProcess        |    Yes     |     No     |     No     |
  Work Field  |                   |            |            |            |
  Invocation  | Detached          |    Yes     |     Yes    |     Yes    |
  Type        |                   |            |            |            |
              | Related           |    Yes     |     No     |     Yes    |
              |                   |            |            |            |
              ------------------------------------------------------------

                Yes=Work field is passed     No=Work field is not passed
 If you ...
          export APPX_FAKE_TIME="2001061510000000"
          appx
 ... you get a date/time of ...
          6/15/2001 8:00am
 ... and the clock ticks forward from there as time goes by.
   BEG READ 0SA USER      HOLD 0      KEY IS
   SET      0SA USER ID            =  0SA USER ID
   SET      0SA USER NAM           =  0SA USER NAM
   END READ 0SA USER
             CNV TEXT <alpha field> = <numeric field>
 SET OWN WF ASCII CODE = 176
 CNV BIN OWN WF ALPHA 1
 ... where WF ALPHA 1 is painted on the report or screen. The other variable
 is a three-digit numeric field.
Is there a general way for the Application designer to manually control
process behavior, based on Security?  For example I would like to 'hide' 
optional children, if the user does not have the required security.  Can I 
determine the security key of the process in ILF?

You can read the 0AD PROCESS file to find out the security class that might 
be assigned to a process.

You can then set up a memory indexed file with a single field of Alpha(4).
Define it as the Record Access security field.  Then, from ILF set the field
to the security code you want to test, write it, and then try to read it back.  If you can't read it back, then you don't have access to that security code.

Details:

1) Create a memory file with one field designated as the RECORD PROTECT
   field, as follows:

2) Make sure that you set the Record Access field for the file as follows:

    Record Protection Fields            
        Delete Protection = blank
        Key Protection = blank
        Record Access = SECURITY_CODE

3) The following ILF code will create and populate the memory file and test
   for a specific code.  The READ returns a true if the user has access to the
   specified code.  The READ returns a false is the user does not have access
   to the specified code.

      SCRATCH  SPF SECURITY            FAIL 0 CACHE? N
      CREATE   SPF SECURITY  SHARE? Y  FAIL 0 CACHE NONE
      *        The write will always succeed
      SET      SPF SECURITY CODE              =      0001
      WRITE    SPF SECURITY               FAIL 0
      *        The read will fail if the user does not have access to code 0001
      SET      SPF SECURITY CODE              =      0001
      READ     SPF SECURITY               HOLD 0 FT 0 BY SECURITY CODE
F     ERROR    User Doesn't Have Access To Code 0001
When you want a QUERY to constrain an INPUT process (the regular INPUT Child 
Constraints can't be satisfied using CC's 'EQ' comparison operator only), you 
can use the following technique:

Create a JOB with Job Steps:
    QUERY
    UPDATE   (uq=query)
    INPUT

All three processes use the same PCF.

The UPDATE's Start of Process is:

      SCRATCH  AAA FILENAME              CACHE? Y
      CREATE   AAA FILENAME   SHARE? Y   CACHE? NOLOAD
      OPEN     AAA FILENAME   SHARE? Y   CACHE? N

The UPDATE's Record frame contains only:

      OPEN     AAA FILENAME   SHARE? Y   CACHE? Y
      WRITE    AAA FILENAME
      OPEN     AAA FILENAME   SHARE? Y   CACHE? N

The INPUT's JobStep's Pre-Invocation sets the following detached workfield:

      SET      AAA WORK USE-CACHED-PCF        =      1

The INPUT's Start of Process contains:

      IF       AAA WORK USE-CACHED-PCF        EQ     1
 T    OPEN     AAA FILENAME   SHARE? Y   CACHE? Y

The INPUT's Post-Invocation sets:

      SET      AAA WORK USE CACHED PCF        =      0

This example does not pass changes to the CACHEed version on to the disk 
version.  You'd have to put code in the INPUT's End of Process for that.
 GOSUB --- GET PARENT PROCESS
 ... then check the values of:
 0AD WORK PROC TYPE
 0AD WORK PROC NAM
 0AD WORK AP
The follow sample will work for any range of numbers where the total numbers
in the range is a maximum of 10,000 (eg., 1 - 10000, 50000 - 60000, 
1678  -11678).  If you use a larger range, you will need to increase the
generating time (TI) by some factor to allow at least one full pass through
the range of numbers.

     *        Set start and end of desired number range.
     SET      --- AI                         =      1
     SET      --- ZI                         =      10000
     *        Use current time to get random number of seconds & hundredths
     *        (WORK RGEN TIME SS defined as date field with seconds only)
     *        (WORK RGEN TIME TH defined as date field with hundredths only)
     SET DATE 1EX WORK RGEN TIME SS
     SET      --- SI                         =  1EX WORK RGEN TIME SS
     SET DATE 1EX WORK RGEN TIME TH
     SET      --- TI                         =  1EX WORK RGEN TIME TH
     *        Add number of seconds to number of hundredths
     COMPUTE  --- TI                         +  --- SI
     IF       --- TI                         LT     1
T    SET      --- TI                         =      1
     *        Set Number counter to one less than specified start of range.
     SET      --- NI                         =  --- AI
     COMPUTE  --- NI                         -      1
     *        Calculate time to stop generator by starting at current time
     *        and increasing it by adding the value in TI to the th's part.
     *        (WORK RGEN RUN END defined as date field with YY thru th)
     SET DATE 1EX WORK RGEN RUN END
     DATE ADD 1EX WORK RGEN RUN END          1  --- TI
     *        Start infinite loop that will exit when end time is reached.
     BEG LOOP LI = 001 TO 001  STEP 000
     COMPUTE  --- NI                         +      1
     *        If number count reaches end of range, go back to start.
     IF       --- NI                         GT --- ZI
T    SET      --- NI                         =  --- AI
     *        If current time has reached end time, exit loop.
     *        (WORK RGEN RUN START defined as date field with YY thru th)
     SET DATE 1EX WORK RGEN RUN START
     IF       1EX WORK RGEN RUN START        GE 1EX WORK RGEN RUN END
F    END LOOP LI
     *          ==>  Resulting generated number is in ---NI
Retrieve and occurrence example:
     TRN WORK DATE occurs 66 times (DD)         
        . . .
     SET --- TEMP 30     =     WORK DATE (note this is a literal)
     SET 0AD ELEMENT NAM = --- TEMP 30
     READ 0AD ELEMENT  HOLD 0 FT 0 BY ELEMENT NAM 
     SET --- AI = 0AD ELEMENT OCC

AI will contain 66 in this example.
Now in 4.2 you can use the two new PDFs --- CURSOR AT APPLICATION and --- CURSOR AT FIELD
just in case the user happened to be sitting on the field of interest.
...
     SET --- NEXT APPLICATION = --- CURSOR AT APPLICATION
     OPEN 0AD ELEMENT
T    SET --- TEMP 30     = --- CURSOR AT FIELD
T    SET 0AD ELEMENT NAM = --- TEMP 30
TT   READ 0AD ELEMENT  HOLD 0 FT 0 BY ELEMENT NAM 
...
I haven't tested this to see if it really works and I'm not sure if the
T    SET --- TEMP 30     = --- CURSOR AT FIELD
would really be required.

     --- Input   STACK (EDIT)
 1) Ensure that the INPUT process does not specify a "Default Mode" 
   (which it always does)
 2) Ensure that the child spec does not specify an "Override Default Mode"
    (which it normally doesn't)
 3) Invoke the INPUT process with an invocation type of SUBPROCESS.  
    (--- DEFAULT MODE has a share class of SUBPROCESS.)
Create a work date field as CC-DD, in the example below this work field is 
WORK DATE and the year I am checking is in WORK YEAR.

Using ILF:

        SET      TRN WORK DATE                      =     TRN WORK YEAR
        SET      TRN WORK DATE                      =     ----0229--------
        IF       TRN WORK DATE                      EQ    ------29--------
T       (the year in WORK YEAR is a leap year)

When 0229 is put in a date field that contains a year, APPX will determine 
if 0229 is valid for that year.  If it is, 0229 will remain.  If not, APPX 
date logic will convert the 0229 to 0301.  In the example above, the first 
SET puts the year in the CC-DD date field.  The second set puts Feb 29 into 
that year.  The IF checks to see if the day is still 29.  If it is, then this 
is a leap year.  
Buttons and Labels on input screens and menus can use html to enhance the
text.  Enter the html code in the Label or Button text field in the object
property(ies).  Example; <html>Request<br>Ship Date will be displayed on two
lines.

----------------
|              |
|  Request     |
|  Ship Date   |
|              |
----------------

The caveat is that the individual lines delineated by the <br> formatting 
may not obey all the label's gui settings, CENTER for example.  

In the case of CENTER the justification is applied to all lines at though 
there all the length of the longest segement.  You can revised the html tag 
to center each line of the label as follows;

<html><p align="center">Request<br>Ship Date
Here is a sample menu structure to create:

Daily
-- Transactions
----- Enter Transactions
----- Print Journal
Monthly
-- Postings
----- Balancing Report
----- Post Transactions

To create this, enter the following in pre-display:
*                                                                         
*        Restore and set defaults for creating CHILD widget records       
*                                                                         
   RESTORE  --- WIDGET                     DEFAULT RECORD                    
   SET      --- WIDGET PARENT TYPE         =      CHILD                      
   SET      --- WIDGET POSITION ROW        =      0                          
   SET      --- WIDGET POSITION COLUMN     =                                 
*                                                                         
*        Create the "Daily" top level pulldown                            
*                                                                         
   SET      --- WIDGET LABEL               =      Daily                      
   SET      --- WIDGET GROUP NAME          =                                 
   SET      --- WIDGET OPTION              =      USER 1                     
   SET      --- WIDGET SHORTCUT            =      D                          
   SET      --- WIDGET ADD TO MENU         =      Y                          
   GOSUB        :WRITE CHILD WIDGET                                          
*                                                                         
*        Create the "Transactions" pullout menu and attach to "Daily"     
*                                                                         
   SET      --- WIDGET LABEL               =      Transactions               
   SET      --- WIDGET GROUP NAME          =      Daily                      
   SET      --- WIDGET OPTION              =      USER 2                     
   SET      --- WIDGET SHORTCUT            =      T                          
   SET      --- WIDGET ADD TO MENU         =      Y                          
   GOSUB        :WRITE CHILD WIDGET                                          
*                                                                         
*     Create the "Enter Transactions" item and attach to "Transacti.." 
*                                                                         
   SET      --- WIDGET LABEL               =      Enter Transactions         
   SET      --- WIDGET GROUP NAME          =      Transactions               
   SET      --- WIDGET OPTION              =      USER 3                     
   SET      --- WIDGET SHORTCUT            =      E                          
   SET      --- WIDGET ADD TO MENU         =      Y                          
   GOSUB        :WRITE CHILD WIDGET                                          
*                                                                         
*        Create the "Print Journal" item and attach to "Transactions"     
*                                                                         
   SET      --- WIDGET LABEL               =      Print Journal              
   SET      --- WIDGET GROUP NAME          =      Transactions               
   SET      --- WIDGET OPTION              =      USER 4                     
   SET      --- WIDGET SHORTCUT            =      P                          
   SET      --- WIDGET ADD TO MENU         =      Y                          
   GOSUB        :WRITE CHILD WIDGET                                          
*                                                                         
*        Create the "Monthly" top level pulldown                          
*                                                                         
   SET      --- WIDGET LABEL               =      Monthly                    
   SET      --- WIDGET GROUP NAME          =                                 
   SET      --- WIDGET OPTION              =      USER 11                    
   SET      --- WIDGET SHORTCUT            =      M                          
   SET      --- WIDGET ADD TO MENU         =      Y                          
   GOSUB        :WRITE CHILD WIDGET                                          
*                                                                         
*        Create the "Postings" pullout menu and attach to "Monthly"       
*                                                                         
   SET      --- WIDGET LABEL               =      Postings                   
   SET      --- WIDGET GROUP NAME          =      Monthly                    
   SET      --- WIDGET OPTION              =      USER 12                    
   SET      --- WIDGET SHORTCUT            =      P                          
   SET      --- WIDGET ADD TO MENU         =      Y                          
   GOSUB        :WRITE CHILD WIDGET                                          
*                                                                         
*        Create the "Balancing Report" item and attach to "Postings"      
*                                                                         
   SET      --- WIDGET LABEL               =      Balancing Report           
   SET      --- WIDGET GROUP NAME          =      Postings                   
   SET      --- WIDGET OPTION              =      USER 12                    
   SET      --- WIDGET SHORTCUT            =      B                          
   SET      --- WIDGET ADD TO MENU         =      Y                          
   GOSUB        :WRITE CHILD WIDGET                                          
*                                                                         
*        Create the "Post Transactions" item and attach to "Postings"     
*                                                                         
   SET      --- WIDGET LABEL               =      Post Transactions          
   SET      --- WIDGET GROUP NAME          =      Postings                   
   SET      --- WIDGET OPTION              =      USER 14                    
   SET      --- WIDGET SHORTCUT            =      P                          
   SET      --- WIDGET ADD TO MENU         =      Y                          
   GOSUB        :WRITE CHILD WIDGET                                          
*                                                                         
END                                                                       
*                                                                         
*        Write WIDGET and increment POSITION ROW to create unique keys    
*                                                                         
   LABEL    :WRITE CHILD WIDGET                                              
   WRITE    --- WIDGET                 FAIL 0                                
-  COMPUTE  --- WIDGET POSITION ROW        +      1                          
F  GOTO     :WRITE CHILD WIDGET                                              
   RETURN    
    SET       --- NEXT DATABASE   =    DB1
    OPEN      TAR CUSTOMER        SHARE? Y FAIL 0
    *
    BEG READ  TAR CUSTOMER        Hold? N
    *
    *         The DB1 Customer file is currently accessible
    *         through the CUSTOMER file name - we just read 
    *         a record from the DB1 Customer file.  Now we 
    *         Want to write this record to the DB2 Customer
    *         file - have to open it first
    *
    SET       --- NEXT DATABASE   =    DB2
    OPEN      TAR CUSTOMER        SHARE? Y FAIL 0
    WRITE     TAR CUSTOMER                 FAIL 0
    F CANCEL unexpected error (duplicate key?) WRITEing CUSTOMER 
    *
    *         Now we have to switch databases again before we
    *         do the END READ
    *
    OPEN      TAR CUSTOMER        SHARE? Y FAIL 0
    END READ  TAR CUSTOMER 

      *
      *         RETURN to Display, 1st time thru
      *
      IF       --- PROCESS CODE               EQ     DISP
      T SET --- OPTION = RETURN
      T SET --- PROCESS CODE = DONE
      *
      *         END to go back to INPUT, 2nd time thru
      *
      F IF --- PROCESS CODE EQ DONE
      FT SET --- OPTION = END 
   SET      --- STREAM OPEN TYPE           =      r
   SET      --- TEMP 256                   =      |ls -la /usr1/appx/
   APPEND   --- TEMP 256                   0      data/C01/AGP/Files/
   APPEND   --- TEMP 256                   0  AGP FILES NAME
   SET      --- STREAM FILE PATHNAME       =  --- TEMP 256
   GOSUB    --- STREAM OPEN
   IF       --- STREAM RETURN CODE         NE     0
T  ERROR    Cannot Get File Listing
T  END
   *    
   SET      --- STREAM EOR SEQUENCE        =      LF
   GOSUB    --- STREAM READ
   *        The results will be in --- STREAM BUFFER         
   DISPLAY  --- STREAM BUFFER              (AT APPEARANCE #    )
  Don't forget to close, GOSUB    --- STREAM CLOSE
 SCRATCH APP FILENAME FAIL 0 CACHE? Y
 CREATE APP FILENAME SHARE? Y FAIL 0 CACHE NOLOAD
 OPEN APP FILENAME SHARE? Y FAIL 0 CACHE? N (for disk version)

 Then to populate:

 BEG AT APP FILENAME IN some constraint
 END AT APP FILENAME IN some constraint
 BEG READ APP FILENAME HOLD 0 KEY IS FILENAME KEY FIELD
 OPEN APP FILENAME SHARE? Y FAIL 0 CACHE? Y (for cached version)
 WRITE APP FILENAME
 OPEN APP FILENAME SHARE? Y FAIL 0 CACHE? N (for disk version)
 END READ APP FILENAME
 OPEN APP FILENAME SHARE? Y FAIL 0 CACHE? Y (so process will use
 cached version)

 Now the data lookup should work on the cached file.

 You could also build a memory file and do the same thing and have the data
 lookup work on the memory file.
    *Save as Default allows you to designate whether you want to re-display on 

    *Auto Read Next allows you to control which record will be read and 
    *Auto Read First allows you to control which record will be read and 
    *Exact Key Required allows you to specify whether or not a complete key must
      *      
      *        Open file in source database      
      *      
      SET      --- NEXT DATABASE              =      AAA      
      OPEN     SPF CUSTOMER  SHARE? Y  FAIL 0 CACHE? N      
      *
      BEG READ SPF CUSTOMER               HOLD 0 KEY IS  CUSTOMER NO
      *
      *        Open file in destination database
      *
      SET      --- NEXT DATABASE              =      BBB
      OPEN     SPF CUSTOMER  SHARE? Y  FAIL 0 CACHE? N
      WRITE    SPF CUSTOMER               FAIL 0
      *
      *        Open file in source database
      *
      SET      --- NEXT DATABASE              =      AAA
      OPEN     SPF CUSTOMER  SHARE? Y  FAIL 0 CACHE? N
      *
      END READ SPF CUSTOMER

     SET      --- STREAM OPEN TYPE           =      r
     SET      --- STREAM READ LENGTH         =
     GOSUB    --- STREAM OPEN
     SET      --- STREAM EOR SEQUENCE        =      LF
     IF       --- STREAM RETURN CODE         NE     0
     *
     *        read tab file record
     LABEL    :NEXT RECORD
     TRAP
     GOSUB    --- STREAM READ
     IF       --- STREAM RETURN CODE         EQ     0
     IF       --- STREAM BUFFER              EQ
     GOTO     :NEXT RECORD 
     In Start of Process�
         CNV BIN --- CDF HEX00                    =  0
         CNV BIN --- CDF HEX0A                   =  10
     In Start if Frame�
         APPEND  --- TEMP 2                            0  --- CDF HEX0A    
         APPEND  --- TEMP 2                            0  --- CDF HEX00

By setting APPX_41_EPS=1 environment variable, you can get previous EP behavior.
This variable, however, can not be set for design. It is for Run time only.

Execution cycle in 4.2 has been changed in 3 areas:
1.      Input execution after OC
2.      Input execution on Delete
3.      Input execution auto execution of child process.

On #1 � input Execution after OC � if you have ORDER1 Input Process, and execute opt1 to run Line Items process, we changed execution cycle when you come back from a child.
The order of the events as follows:
1.      Read the PCF record with HOLD
2.      Executes Post PCF Read
3.      Executes Post Invocation of the Child
4.      Executes Select Image
5.      Executes Pre-Display/Verify EP
6.      Executes Pre-Display
7.      We display the Screen

4 � 6 � is what changed in 4.2.

On #2 � Input Execution on Delete � if you delete a record, Appx will execute Pre-Update EP, after Delete � Post_PCF Update EP.
Prior to 4.2 � Pre-PCF Update Ep wasn�t executing.

On#3  Input Execution auto execution of child process � Key change, record delete (for example, you have ORDER1 and ORDER2 as an AC to ORDER1. If you delete ORDER1 record, you need to delete all corresponding ORDER2 records).
It looks to see if ORDER2 needs to be run.
It executes ORDER2 in autoexecute, it goes through all the steps to delete ORDER2 records.

It executes:
Post PCF read
Pre PCF Update
Post PCF Read
Delete � Post PCF Update

It will execute all these EP�s for each line item.

In 4.1, it wasn�t executing Post PCF Read and Pre PCF Update.
First a short introduction on the choice of character set and length semantics: 
Using Unicode as a character set will allow you to store any character, 
not just the western European characters you are normally limited to.

Unicode is a multi-byte character set which means that a single character could use more than a single byte. So what do you mean by VARCHAR2(10)? 
Is this 10 characters or 10 bytes? 
This used to be the same with our single byte character set, but with UTF8 this is no longer true. 
You can specify VARCHAR2(10 BYTE) or VARCHAR2(10 CHAR) if you want to be specific. 

However, APPX doesn�t use this syntax and does not specify either. 
This is where the NLS_LENGTH_SEMANTICS parameter comes in. 
You can set this to BYTE or CHAR basically defining which one of the two is the default when not specifying it explicitly.

A default Oracle installation will use BYTE semantics which will work with APPX.  
However, if the default is changed to CHAR semantics, then APPX won't work without setting the following environment variable:

NLS_LENGTH_SEMANTICS=BYTE
======================================================================
SUBROUTINE  Process Name:     GET PROCESS ID

      GOSUB    --- GET CONFIGURATION INFO 
      SET      --- CONFIG TYPE                =      PID 
      READ     --- CONFIG                 HOLD 0      BY CONFIG TYPE 
F     CANCEL    unexpected error trying to READ "--- CONFIG" 
      SET      --- TEMP 32                    =  --- CONFIG DATA 
      *        --- TEMP 32 contains the unique Process ID 

====================================================================== 
The following list of shortcuts can be used while entering statements in the ILF editor.

S  =  SET
W  =  WRITE
A  =  APPEND
G  =  GOSUB
I  =  IF
T  =  TRAP

BA (or BEG A) =  BEG AT
BR (or BEG R) =  BEG READ
BL (or BEG L) =  BEG LOOP

EA (or END A) =  END AT
ER (or END R) =  END READ
EL (or END L) =  END LOOP

CA    =  CALC
CO    =  COMPUTE
READN =  READNEXT
R     =  READ
REW   =  REWRITE

RECIEVE = RECEIVE   (auto correct)
COPY and GOSUB are almost identical in that they both bring the code inline 
to your process.  In fact, when you code something like:

 GOSUB    XXX SUBROUTINE

where SUBROUTINE is *not* a label in the current event point, then APPX will 
create

 LABEL    SUBROUTINE
 COPY     XXX SUBROUTINE
 RETURN

The major difference between COPY and GOSUB is that GOSUB has its own set of 
T/F flags, whereas COPY just copies the requested code into the event point 
at that location, and if there are any T/F flags involved, the copied routine 
better know about them.  Example:

   READ   <some file>
F  COPY   <routine a>

The code in routine <routine a> will have the F flag set in the first position 
when it starts running, and any T/F flags it changes will be visible to the 
code following the COPY.  If the copy was a GOSUB instead, then in <routine 
a>, the first T/F flag would not be set, and any T/F  flags it changes would 
*not* be visible to the statements following the GOSUB. 

A SUBR is another process invocation, so:

 - the code exists as a separate process, which is sometimes required.
   For example, you can call SUBR within a BEG READ/END READ loop, and
   the routine can also do a BEG READ/END READ on the same file without
   any problems.

 - you can control sharing via the SUBPROCESS/RELATED/DETACHED invocation

 - the code is *not* compiled into the calling program, thus reducing EM
   size (but who cares, really).

 - you cannot exit the routine with a RETURN, you must have an END or
   EXIT, or just run out of statements.

 - takes longer to invoke, as a separate process needs to be brought
   into memory and control passed to it, and then returned to the caller.
   Not a problem for data entry programs but can add run time if it's
   in a update & gets invoked hundreds of times.

Because of the difference in exiting a SUBR (with END/EXIT) vs. a GOSUB (with 
RETURN), you can't really call the routine one way or the other.  You must 
decide if it's going to be invoked as SUBR or GOSUB, and code accordingly.  
If a SUBR attempts to exit with RETURN, you will get a run time error, however,
if a GOSUB encounters an END/EXIT, then you have just ended the execution of 
the entire Event Point, not just that subroutine.  This is a subtle programming 
error that can lead to difficult to track down bugs, ie, sometimes a post just 
skips part of the updating for a record because someone put an END instead of 
RETURN in a GOSUB'd routine.

As to which one to use:

 - COPY if you just want to bring in some straightforward code, i.e., for
   this current ORDER2 record, read the ORDER1, CUSTOMER and PRODUCT files.

 - GOSUB if you need to preserve the T/F flags

 - SUBR if you *need* the special advantages it offers.

This concept deals with variable values and memory as you branch into and  
return from subroutines.  If you have a process that is using --- AI as a 
counter and at some point in the code you branch into a subroutine and return, 
the variable --- AI may have been changed (or stepped on) by the subroutine.  
That is because GOSUBs and COPYs bring the code into the current process.  
You can have the subroutine STORE and RESTORE any variables it uses, but that 
only works one level deep.  

If a subroutine is called by a GOSUB and it in turn calls another subroutine 
with a GOSUB, then the STORE in the second subroutine will step on the STARE 
done by the first subroutine.  This is because there is only one STORE/RESTORE 
area per variable/process. 

Example:

Process: TEST
SET      --- AI                 =     10
GOSUB    AAA DO SOMETHING
SET      --- BI                 = --- AI
*
END
*
LABEL    DO SOMETHING
STORE    --- AI
SET      --- AI                 =     20
GOSUB    AAA DO SOMETHING ELSE
RESTORE  --- AI
RETURN
*
LABEL    DO SOMETHING ELSE
STORE    --- AI
SET      --- AI                 =     30
RESTORE  --- AI
RETURN

So, instead of --- BI getting a value of 10, it would get a value of 30.  This 
is because the second GOSUB'd routine wrote over the STORE buffer created by 
the first routine.

On the other hand, if you use SUBR calls, then each SUBR routine contains it's 
own STORE/RESTORE buffer area that can never step on the parent process 
STORE/RESTORE buffer or be stepped on by any child process the SUBR calls.  
This way, you are safe to use any variable as long as you STORE it first and 
RESTORE it when done.  Process sharing characteristics are also handy for this.
If you call SUBRs as related, and SUBPROCESS variables are local and any 
RELATED variables are shared.  This also allows for easy recursion.

Text Position    WIDGET ALIGN HORIZ  WIDGET ALIGN VERT
---------------- ------------------  -----------------
{null}           {null}              {null}
CENTER           CENTER              CENTER
TOP              CENTER              TOP
RIGHT            RIGHT               CENTER
BOTTOM           CENTER              BOTTOM
LEFT             LEFT                CENTER
UPPER LEFT       LEFT                TOP
UPPER RIGHT      RIGHT               TOP
LOWER RIGHT      RIGHT               BOTTOM
LOWER LEFT       LEFT                BOTTOM

                 WIDGET TEXT  WIDGET TEXT  WIDGET TILING 
Icon Position     POS HORIZ    POS VERT     MODE 
---------------- -----------  -----------  -------------
{null}           {null}       {null}       {null}
BEHIND TEXT      CENTER       CENTER       {null}
ABOVE TEXT       CENTER       BOTTOM       {null}
TRAILING TEXT    LEFT         CENTER       {null}
BELOW TEXT       CENTER       TOP          {null}
LEADING TEXT     RIGHT        CENTER       {null}
ABOVE & LEADING  RIGHT        BOTTOM       {null}
ABOVE & TRAILING LEFT         BOTTOM       {null}
BELOW & TRAILING LEFT         TOP          {null}
BELOW & LEADING  RIGHT        TOP          {null}
EXPAND TO FILL   {null}       {null}       EXPAND
EXPAND PROP'L    {null}       {null}       TILE

Here is an example from 1EX:

I added the following code to the ORDER2 Input Process, in 1EX, frame 200,
Option Intercept:

      SET      1EX  WORK LOG                  EQ     0

      *        Copy current line
      IF       --- OPTION                     EQ     USER 1

T     STORE    1EX ORDER2                     RECORD

T     BEG LOOP WI = 000 TO 001  STEP 000

T     COMPUTE  1EX ORDER2 SNO                 +      1

T     WRITE    1EX ORDER2                 FAIL 0

TT    SET      1EX WORK LOG                   EQ     1

TT    END PROC

Then in the parent process - INPUT ORDER1, i went to the  AA and gave it a

child ID of TSTT.

Then in the Post Invocation of the Child Rule i added:

    IF       1EX WORK LOG                   EQ     1

T   SET      --- NEXT CHILD ID              =      TSTT

It causes the child process to re-display silently and the newly added record

is displayed to a user.

When you create the button (or any other widget), assign a name on the
Button Properties screen.

In Pre-Display, based on the condition you wish to check:

     SET     --- WIDGET NAME =  <Name you gave the widget>
     READ    --- WIDGET HOLD 1 FT 0  BY WIDGET NAME
F    CANCEL      Widgit not found
     IF          <Condition you need to test on>
T    SET     --- WIDGET COLOR EN FG R  = <red value: 0-255>
T    SET     --- WIDGET COLOR EN FG B  = <blue value: 0-255>
T    SET     --- WIDGET COLOR EN FG G  = <green value 0-255>
T    SET     --- WIDGET COLOR EN BG R  = <red value: 0-255>
T    SET     --- WIDGET COLOR EN BG B  = <blue value: 0-255>
T    SET     --- WIDGET COLOR EN BG G  = <green value 0-255>
    *       Set the default color for button 
F    SET     --- WIDGET COLOR EN FG R  = <red value: 0-255>
F    SET     --- WIDGET COLOR EN FG B  = <blue value: 0-255>
F    SET     --- WIDGET COLOR EN FG G  = <green value 0-255>
F    SET     --- WIDGET COLOR EN BG R  = <red value: 0-255>
F    SET     --- WIDGET COLOR EN BG B  = <blue value: 0-255>
F    SET     --- WIDGET COLOR EN BG G  = <green value 0-255>
   *
     SET     --- WIDGET COLOR EN FG NL = 1   <so color is not ignored>
     SET     --- WIDGET COLOR EN BG NL = 1   <so color is not ignored>
     REWRITE --- WIDGET FAIL 0

The color values are the decimal values for the colors.  For example; hex 
color value #FFFFFF (white) is decimal value 255 for red, green, and blue.

The FG fields set the text color (foreground) on the button.  The BG fields 
set the background color.  When you save the ILF READ and WRITE statements, 
if it says the widget file could not be found, use Opt 88 to save the code.
     PRE-DISPLAY
     PRE-DISPLAY/VERIFY
     VERIFY
 Create a detached Optional Child:
               --- SUBROUTINE   HELP (PROCESS)
 Give it a Pre-Invocation ILF command:
               GOSUB    --- HELP (GRAB CURRENT PROCESS)
            SET   --- EXACT KEY REQUIRED   =    Y
            SET   --- AUTO READNEXT        =    N
Setting the field to OK INPUT (or maybe Entry Level=0) will make the 
field editable. But, then you will need the following trick to actually 
get the changed value to save because APPX always restores the constraint 
field values just before rewriting the PCF record.

In Pre-Update
STORE   XXX HOLD    RECORD

In Post-Update
READ    XXX HOLD (with hold) 
RESTORE XXX HOLD    RECORD
REWRITE XXX HOLD
Text Position    WIDGET ALIGN HORIZ       WIDGET ALIGN VERT
---------------- ------------------------ --------------------
{null}           {null}                   {null}
CENTER           CENTER                   CENTER
TOP              CENTER                   TOP
RIGHT            RIGHT                    CENTER
BOTTOM           CENTER                   BOTTOM
LEFT             LEFT                     CENTER
UPPER LEFT       LEFT                     TOP
UPPER RIGHT      RIGHT                    TOP
LOWER RIGHT      RIGHT                    BOTTOM
LOWER LEFT       LEFT                     BOTTOM

Icon Position    WIDGET TEXT POS HORIZ    WIDGET TEXT POS VERT    WIDGET TILING MODE
---------------- ------------------------ ----------------------- -------------
{null}           {null}                   {null}                  {null}
BEHIND TEXT      CENTER                   CENTER                  {null}
ABOVE TEXT       CENTER                   BOTTOM                  {null}
TRAILING TEXT    LEFT                     CENTER                  {null}
BELOW TEXT       CENTER                   TOP                     {null}
LEADING TEXT     RIGHT                    CENTER                  {null}
ABOVE & LEADING  RIGHT                    BOTTOM                  {null}
ABOVE & TRAILING LEFT                     BOTTOM                  {null}
BELOW & TRAILING LEFT                     TOP                     {null}
BELOW & LEADING  RIGHT                    TOP                     {null}
EXPAND TO FILL   {null}                   {null}                  EXPAND
EXPAND PROP'L    {null}                   {null}                  TILE
   SET  --- WIDGET INVIS = Y

  www.appx.com > Support > Online Manuals > Application Design Manual

            http://www.appx.com/manuals/appl-dsgn/drm282.html
Date masks on OUTPUT Report Page Headings can be controlled by means of a
System-Parameter, or Application-override Date masks, and an environment
variable 'APPX STD PGH MASK'.

For Example:

If I have no System or Application date mask override set, and I run an
OUTPUT with a standard page heading, I get a page heading date (for example)
of "03/25/1999 00:16 23.83"

If I had set my System or Application date mask to 

"06/05/07 - 04:03:02.01"

I get a page heading date of

"03/25/99 - 00:16 23.83"

The ILF code ...

         CNV BIN  --- TEMP 1           = 27

 ... puts an "ESC" Escape character (hex(1b)) into TEMP 1.  You can then SET
this into an Alpha field, append other control codes as necessary, then embed
Alpha fields constructed in this manner in our OUTPUT report.

 ('ESCape' = Hex(1b) = 16 + 11 = decimal(27).)

See the ILF manual on the CNV BIN verb, for more detail on how it works.  

 www.appx.com > Support > Manuals > Application Design > Search > CNV BIN

On APPX/Windows platforms, you'll need to send a 'Form Control' of "-raw", in
order to tell the Windows Print Spooler not to filter out your escape codes.

WARNING:  Winprint interfaces to the printer's printer driver.  Some printer
drivers don't honor '-raw' pass through of hex codes.  The only way to find 
out is to try it.
           SET --- ALTERNATE IMAGE NUMBER = 0
           SET --- ALTERNATE IMAGE NUMBER = 1
     QSORT SUBT
     QSORT SUBT NEW PG
     NO       N,N
     STANDARD Y,N
     NEW PAGE Y,Y
For a new line, use CTL RETURN.

<p>               - new paragraph (does not require an ending </p>)
<pre> ... </pre>  - new paragraph with Courier font and fixed spacing
&nbsp             - fixed space (needed when not using <pre>)
<b> ... </b>      - bold
<i> ... </i>      - italic
<li> ... </li>    - each bullet
<ul> ... </ul>    - to indent bullets
<font size="n"> ... </font> where n=1-9 (1=8,2=10,3=12,4=14,5=18,6=24,7=36pt)

A good example of usage to look at is the new IF DIFF statement under 
System APPLICATION DESIGN, Subsystem ILF STATEMENTS.  
Remember, in INQ mode, you see the HTML tags applied; 
in CHG mode, you see the actual HTML tags coded.

   RESTORE  --- WIDGET                     DEFAULT RECORD
      SET      --- WIDGET PARENT TYPE         =      WIDGET
      SET      --- WIDGET WIDGET TYPE         =      PICTURE
      SET      --- WIDGET POSITION ROW        =      1
      SET      --- WIDGET POSITION COLUMN     =      2
      SET      --- WIDGET LOC OFFSET COL      =      -100
      SET      --- WIDGET SIZE ROWS           =      3
      SET      --- WIDGET SIZE COLUMNS        =      15
      SET      --- WIDGET RESOURCE TYPE       =      RESOURCE
      SET      --- WIDGET RESOURCE NAME       =      <your resource name>
      SET      --- WIDGET RESOURCE AP         =      <your app>
      SET      --- WIDGET TEXT POS HORIZ      =
      SET      --- WIDGET TEXT POS VERT       =
      SET      --- WIDGET TILING MODE         =      TILE
      WRITE    --- WIDGET                 FAIL 0
 <br> is ignored...  
 <i> italics </i> <em> italics </em> <tt> tele-type font (courier) </tt> <small>
 next smaller font </small>

        APPX_RUN_MEM=2097150

      *                                                                         
      *        Customer of interest were supplied in an earlier input.          
      *                                                                         
      BEG READ DAR MCUST                  HOLD 0 KEY IS  MCUST CUSTOMER NO      
      BEG AT   DAR TRANSACT IN DAR MCUST CUSTOMER NO                            
      END AT   DAR TRANSACT IN DAR MCUST CUSTOMER NO                            
      BEG READ DAR TRANSACT               HOLD 0 KEY IS  TRANSACT KEY           
      GOSUB    --- PROCESS QUERY RECORD                                         
      END READ DAR TRANSACT                                                     
      END READ DAR MCUST                                                        
    Primary
    Alternate/Unique
    Alternate
    Alternate/Forced

APPX      Application Excellence

AA        Additional Attributes
AC        Automatic Child Process
APPXPATH  Default directory location for APPX applications and data
CC        Child Constraint
CDF       Comma Delimited File
DD        Data Dictionary
DLU       Data Look Up
EM        Executable Module
EP        Event Point
FLEP      File Level Event Point
FMS       File Management System
GUI       Graphical User Interface
ILF       Integrated Language Facility 
LFN       Logical File Name (If you use symbolic links or the "Use DB" feature,
          many logical file names can map to the same physical file.  
          A logical file name is (roughly) an application ID + database ID + filename) 
OC        Optional Child Process
PCF       Process Control File
PDF       Pre-Defined Field

In file-level Event Points, does APPX report reliably on the 'real' mode of 
the I/O?

For example, if we're adding a record in an INPUT process, and a file-level 
event point fires incrementing a value in a parent table, how does the  file-
level Event Point for the event report set flags indicating what's going on?

When the event triggering the firing of the File EP's is an ILF statement, 
then INTERACTIVE PHASE and MODE both are inferred from the ILF statement 
itself:

   WRITE - Add
   REWRITE - Change
   DELETE - Delete

This is true even if the ILF statement is itself part of a File EP.

Another interesting point:  In a File's POST READ event point, if it fired off
because of an ILF statement, then ...

 - INQUIRE is inferred if the read operation was without a hold on the record
 - CHANGE  is inferred if the read operation was with a hold on the record.

This then results in both INTERACTIVE PHASE and MODE being set accordingly.

1) The MODE and INTERACTIVE PHASE are not what they are in the Input process.
   You will not see DATA SCROLL for instance.

2) Multilevel process families.  For example, if you add an order in Order
   Entry:

You add some header info, then lineitem info, then to the header and down to 
charge/allowance items, then back to the header and down to order comments, 
then back to the header to complete the order.

      You will get several file level event points fired.  When you go from
      the header down to the lineitems while adding the order, APPX will write
      the order header PCF and fire the event points with a MODE=ADD, but the 
      order is not done yet.

      It will then re-trigger the file event points several more times in 
      MODE=CHANGE as it resaves the PCF during the remaining entry of the 
      order including the exit from the final frame of the order header to 
      complete the order.

      So, if you want to do something when the order is completed, you need   
      some way to detect a completed order other than MODE=ADD in the file 
      level event point.

      Also, File Event Points are fairly isolated from the trigger process 
      that fires them.  You can't set a workfield in your input process and 
      check it in the file event point.  Only the PCF record is shared.
      will be lost anyway - we don't support alpha channels in PNG files),or 
      have 16 bit color depth will have to be uncompressed.
      majority of JPEG images.  We also support progressive JPEG compression.

      JPEG images can be packaged in several different file formats. We
      support all common JPEG file formats, and will read resolution 
      information from the following types:

       - JFIF,which is generated by a wide variety of imaging applications. 
       - JPEG files written by Adobe Photoshop and other Adobe applications.
      format, the entry in the GIF file called "LZW minimum code size" must 
      have a value of 8 bits.
      Unfortunately,there is no easy way to determine this value for a certain 
      GIF file. An image which contains more than 128 distinct color values 
      will always qualify (e.g.,a full 8-bit color palette with 256 entries). 
      Images with a smaller number of distinct colors may also work,but it is 
      difficult to tell in advance because graphics programs may use 8 bits or 
      less as LZW minimum code size in this case,and we may therefore reject 
      the image.
      The following trick which works in Adobe Photoshop and similar image 
      processing software is known to result in GIF images which are 
      accepted:
         load the GIF image,and change the image color mode from "indexed" 
         to "RGB". Now change the image color mode back to "indexed",and 
         choose a color palette with more than 128 entries (for example the 
         Mac or Windows system palette,or the Web palette).
      The image must not be interlaced.
      compression schemes: 
       - uncompressed 
         CCITT (group 3,group 4,and RLE) 
         ZIP (=Flate) 
         LZW (with restrictions) 
         PackBits (=RunLength) 
         other compression schemes are handled by uncompressing. 
      color: 
         black and white 
         grayscale 
         RGB 
         CMYK 
            any alpha channel or mask which may be present in the file will be 
            ignored.
      TIFF files containing more than one image 
      Color depth must be 1,2,4,or 8 bits per color sample (this is a 
      requirement of PDF).
      Multi-strip TIFF images are converted to multiple images in the PDF 
      file which will visually exactly represent the original image,but can 
      be individually selected with Acrobat s TouchUp object tool. Multi-
      strip TIFF images can be converted to single-strip images with the 
      tiffcp command line tool which is part of the TIFFlib package. The 
      Image-Magick tool always writes single-strip TIFF images. Some TIFF 
      features (e.g.,CIEL*a*b*color space,JPEG compression)and certain 
      combinations of features (e.g.,LZW compression and alpha channel or 
      mask, LZW compression and tiling)are not supported. 
  1 - draw horizontal grid lines at grid boundaries
  2 - draw vertical grid lines at grid boundaries
  4 - label horizontal grid lines
  8 - label vertical grid lines
 16 - subdivide grid height into 1/10 intervals
 32 - subdivide grid width into 1/10 intervals
 64 - draw outlines around all widgets

        IF   XYZ  FOO      RS  .*123.

--- INTERACTIVE PHASE is set during input processes and indicates which data
entry phase is currently in force. It works with  --- MODE and, although they
work together, each has a specific use.

MODE is determined when the user selects an input process from a menu and
selects a mode option (ADD, CHG, DEL, or INQ). INTERACTIVE PHASE determines
what the user may do while in that mode. For example, if you are in ADD mode
entering data into a scrolling frame, you can move the cursor to a previously
added record and select the change item option. At this time you will still be
in add mode, but the interactive phase will change from data addition to data
modification. 
       "Enq: (FATAL ERROR): 0781-024 Cannot write anymore to
       /var/spool/qdaemon/to4mZM"

        APPX_TRAILER_COUNT=40
        APPX_LABEL_MEMORY=1
 appx -l=logfile
In the course of Appx/Clients attaching to a WinAppxD Appx/Server, with 
APPX NET_LOG enabled, the following NET LOG entries can come up.  Here are 
explanations:

        SetProcessWindowStation() returned 1, (err=122)
        CreateDesktop() returned 168 (err=122)

 These aren't errors.  They would be errors if they had returned 0.

        recv() failed, exiting, errno = 10054

 "An existing connection was forcibly closed by the remote host."
                                        (From the MS Win32 API Error Codes)

This can be caused by something in the network (aka an 'assassin') sending a 
RESET packet.  This kills WinAppxD, and therefore all links between 
Appx/Clients and the Appx/Server.  The Appx/Server may or may not be able to 
manually restart, depending on whether something in the network is holding the 
old port open or not.  If the port is being held open, the Appx/Server can't 
grab it again.

That "something in the network" could be routers, modems, or other equipment 
in the network.
                 $display:         (can look like "Sdisplay")

 Windows cannot find '$display:'. Make sure you typed the
 name correctly, and then try again. To search for a file,
 click the Start button, and then click Search.

                    OK
     Appx - 41440:  appx.exe - application error

  The instruction at 0x004992b0 referenced memory at 0x004992b0.   
  The required data was not placed into memory because of an 
  I/O error status of 0xc000020c.

                 APPX_DISABLE_DYNAKEYS=1
Bruce Johnston 15, '04:
You can also create a dynamic index via ILF (at least from 4.1 through 4.2.2).
Given two fields, DGA FDRFEPR FED WASTE PRE and DGA FDRFEPR FED WASTE SUF, if I want to sort by the PRE and then by the SUF, both in ascending order, I use the following...
      PASS     DGA FDRFEPR FED WASTE PRE      FIELD            SHARE? N         
      PASS     DGA FDRFEPR FED WASTE SUF      FIELD            SHARE? N         
      CALL         ,PI_DYNA_BLD               RESIDENT? N  END? N  FAIL 0       
If I wanted to change the default order of any to reverse it I'd simply double up its PASS command as in...
      PASS     DGA FDRFEPR FED WASTE PRE      FIELD            SHARE? N         
      PASS     DGA FDRFEPR FED WASTE SUF      FIELD            SHARE? N         
      PASS     DGA FDRFEPR FED WASTE SUF      FIELD            SHARE? N         
      CALL         ,PI_DYNA_BLD               RESIDENT? N  END? N  FAIL 0       
which gives the records sorted by the PRE in ascending order followed by the SUF
in descending order.

I believe that it was Korry who first told me this.
The maximum file size is dependent on the release of APPX and the operating
system.  The following chart shows the maximum file sizes allowed for each
operating system based on the release level of APPX.

              Maximum file sizes by release

Release   Windows    AIX       Solaris   HP/UX     Linux
=======   ========   =======   =======   =======   =======  
4.2       2 GB       4 GB      4 GB      4 GB      4 GB
4.1.a     2 GB       4 GB      4 GB      4 GB      2 GB
4.1       2 GB       4 GB      4 GB      2 GB      2 GB
prior     1 GB       2 GB      2 GB      2 GB      2 GB
 time(seconds) unlimited file(blocks) 2097151 data(kbytes) 131072 stack(kbytes) 32768 memory(kbytes)32768 coredump(blocks) 2048 nofiles(descriptors) unlimited

 time(seconds) unlimited file(blocks) unlimited data(kbytes) 131072 stack(kbytes) 32768 memory(kbytes) 32768 coredump(blocks) 2048 nofiles(descriptors) unlimited
                  Fuser �u /user/appx/data/VV/AAA/Data/Bugvar.dat

                  /user/appx/Data/VV/AAA/Bugvar.dat: 15846(tom)    18211(appx)

              Toolkit.getDefaultToolkit().beep()
        SUBR --- LOAD URL ON CLIENT.
        SUBR --- CHECK GUI CLIENT     SUBPROCESS  END? N
        IF   --- RETURN CODE             EQ    1
  T     it's the java client
  F     it's not
To determine your environment variables under Unix, perform:

       RUN          set > /tmp/env.txt

To determine your environment variables under APPX for Windows:

       RUN          cmd /c set >C:\tmp.txt
       RUN          wordpad.exe C:\tmp.txt

 (Under Windows 9x, use command.com rather than cmd.exe.)

If you're running APPX/Client, have the first RUN redirect standard out to a  
file in a client-accessible directory, then run an editor on that file.

To get the environment variable using ILF, try;

      SET      --- TEMP 80          =      cd /tmp;
      APPEND   --- TEMP 80          1      set > env.tmp;
      APPEND   --- TEMP 80          1      grep APPX env.tmp >
      APPEND   --- TEMP 80          1                env.txt   ;
      APPEND   --- TEMP 80          1      rm env.tmp
      RUN      --- TEMP 80
   1) Download a fresh copy of the APPX Java Client ('javacli.exe').

   2) Create a new directory (renaming or deleting the old one if necessary).
      Run this 'javacli.exe', installing it into this new directory.

   3) Reboot the client PC.

   4) Try to run 'appxjava.exe' from the new directory.

   5) If it fails, from a DOS window, do a "set" command.  Email the value
      of IBMHPJ_OPTS to us at techsupp@appx.com, along with the location of the
      directory into which you installed the Client.
Over the past 6 months, our APPX login times have steadily lengthened. 

Normally this symptom is due to a growing USAGE file.  Other likely events;

- network traffic in general has increased on your network

- more users in APPX

- more PC�s on your network

- do you have the APPX client stored on a local disk on each client PC, or
  are  you retrieving it from the network any time someone logs in?  (See the
  WinAppxD FAQ, ftp.appx.com/pub/documents/winappxd-faq.txt, section 2.12: 
              "Automatically update Presentation Client".)

- It's also possible that you have a DNS or WINS issue 
Example of a batch file that can start APPX and automatically update the 
APPX/Client to the most recent version prior to logon:

rem  AppxJAVA.bat
rem  Batch file to launch Appx Java Client and keep it updated.
xcopy x:\Appx\StartUp\Images\splash.jpg c:\"Program Files"\AppxClient\
                        themes\default\ /d
xcopy x:\Appx\StartUp\login.ini c:\"Program Files"\AppxClient\ /d
xcopy x:\Appx\StartUp\JavaClientUpdate\AppxClient.exe c:\"Program Files"\
                        AppxClient\ /d
xcopy x:\Appx\StartUp\JavaClientUpdate\Appx.jar c:\"Program Files"\
                        AppxClient\ /d

"C:\Program Files\AppxClient\AppxClient.exe" -cols=80 -rows=25
                 -title="Appx -$(user) on $(host):$(port), PID $(pid)
exit

The following batch file does the same for the Appx Windows Client.

rem AppxWin3.bat
rem 09/03/99 PAK
rem
rem Batch file ran on each client at startup of Appx
rem i.e., the Appx Desktop shortcut should point to this file
rem
rem XCOPY switches:
rem /d - Copies only those files whose source time is newer than
rem      the destination file.
rem /i - If destination does not exist and copying more than one file,
rem      assumes that the destination must be a directory.
rem /u - Copies only files that already exist in destination
rem
rem Copies the Latest Version of Appx to your computer!
rem
xcopy x:\appx\appx.exe c:\Appx\Win32\ /d

md c:\Appx\Win32\data
xcopy x:\appx\startup\winprint.exe c:\Appx\Win32\data\ /d

rem for WinNT, HOSTS file is in: Winnt\system32\drivers\etc\
xcopy x:\Appx\Startup\Hosts.* c:\Winnt\system32\drivers\etc\ /d /i
xcopy x:\Appx\Startup\Hosts   c:\Winnt\system32\drivers\etc\ /d
start c:\Appx\Win32\Appx.exe -c
We run a job for a post and the action log normally behaves correctly, 
but on occasion no log is produced.  But in a subsequent job for 
another group, the action log contains items (usually Warnings) for 
this post, as well Warnings from the first post.
 1) In Control Panel > Administrative Tools > Data Sources(ODBC) > 
          System DSN tab => Remove the AppxODBC record. 1) Uninstall AppxODBC.
 2) If 'C:\appx.env' exists, delete or rename it.
 3) Delete appxodbc directory tree (which contains the 'appx.dbs' tree).
 4) Search for and delete appxodbc.dll and appxsetp.dll.
 5) Reboot.
 6) Reinstall AppxODBC from a downloaded AppxODBC installation package.

         http://board.appx.com/faq/cache/232.html 

   $HOME/.appx/
   C:\Documents and Settings\{yourWindowsID}\.appx\
   C:\WINNT\.appx\

      PASS     Rq: Buffer                     FIELD            SHARE? Y

      PASS     Op: Total Chars in Clipbrd     FIELD            SHARE? Y

      PASS     Op: Max Num Chars to Read      FIELD            SHARE? N

      GOSUB    --- READ FROM CLIENT CLIPBOARD                           
      PASS     --- RI                         FIELD            SHARE? Y
      PASS     --- CI                         FIELD            SHARE? Y
      GOSUB    --- GET SCREEN SIZE 
Is Appx going to be affected by the new Daylight Savings Time?

APPX does not keep time � it simply reads what the operating system provides. 
As long as you have patched your OS properly, there will be no issues as far as 
APPX is concerned.

It means that Appx found an unexpected entry in a "scope list".  
When you open a file, Appx creates a "logical file block" (LFB) to keep track
of that file.  Every file is opened at some particular scope - when that scope
ends, the file is closed and the LFB is discarded (a scope is something like
"the most recently invoked related process", "the current event point", or
something like that).  The LFB is linked into a list of all LFB's belong to a
given scope.  This message means that Appx was processing a scope list and
found an LFB that should have been linked into a different list (because it
has the wrong scope).

It could be related to FLEP bug.
                     export APPX_IMPORT_COMMIT=5000

                     export APPX_IMPORT_COMMIT=5000      

                      $APPXPATH/appx.env
                      $HOME/appx.env

                      ORACLE SID=APPX
                      APPX DBG CODE=OxFFFFFFFF
                      Etc.
The --- COMMIT MODE pdf has four valid values.  (You may see AUTOCOMMIT as 
well, but it's not implemented yet):

 MANUAL     -  Appx will not automatically COMMIT your changes.  You must use
               the COMMIT statement.

 END        -  Appx COMMITs your changes when the process ends.

 PCF CYCLE  -  Appx COMMITs your changes as you progress from PCF record to 
               PCF record.

 COMPATIBLE -  Appx COMMITs your changes as soon as -all- record locks are 
               released.

Appx never automatically issues a ROLLBACK.  Based on the structure of your 
application, there may be other places where you want to COMMIT a transaction.  
That's what the COMMIT statement is for.  One thing to keep in mind is that the
frequency of COMMITs will affect performance.  The more COMMITs you do, the 
slower your application will be.  For interactive processes, you can probably 
ignore the performance issue, but for batch-mode operations, COMMITing too 
often can really slow things down.

Another issue to be aware of is that AppxIO files do not support transaction 
processing.  If you ROLLBACK a change to an RDBMS-hosted file, any changes made 
to AppxIO will not be rolled back.  Related to this is the issue of visibility.  
Changes made to an RDBMS-hosted file are invisible to other users until they 
are committed.  Changes made to an AppxIO-hosted file are visible immediately.

Appx also supports save-points.  A save-point is a partial transaction.  You 
mark the beginning of a save-point with the SAVEPNT statement - the only 
argument is a name of your choosing. Executing a SAVEPNT tells the RDBMS that 
it should write a marker into the current transaction.  If you find that you 
want to ROLLBACK part of a transaction, you can specify a save-point name in 
the ROLLBACK statement.  The transaction is still open and you can commit other 
changes, but changes made since the save-point was created are lost.
Example: moz /users/pat> appx �u

Usage: -u                          list these options
       -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 UNIXIO format
       -e=<data_file_name>         convert a UNIXIO file into a flat format
       -v=<data_file_name>         verify the integrity of a UNIXIO file
       -an=<data_file_name>        analyze a UNIXIO file
       -l=<log file name>          start a license server

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 will be used.

If no application_id is specified, the startup application and menu for the 
database will be 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.
 1) Enter a server name in the Appx/Oracle FMS group (either an Oracle
    SID, or the name of a remote server as described below).
 2) If you leave the server name blank, the OCI uses the environment
    variable $TWO_TASK to locate a remote server.
 3) If you leave the server name blank and $TWO_TASK is not defined, the
    OCI uses the $ORACLE_SID environment variable to locate a local
    server.
       $ORACLE_SID:$ORACLE_HOME:<N|Y>:

     oracle:/opt/oracle/product/9.2.0:N
      ORACLE.INTERNAL.APPX.COM =
      (DESCRIPTION =
      (ADDRESS_LIST =
      (ADDRESS = (PROTOCOL = TCP)(HOST = badger.appx.com)(PORT = 1521)))
      (CONNECT_DATA =
      (SERVER = DEDICATED)
      (SERVICE_NAME = oracle)))
 1) If you know your Oracle server is installed on the same machine as
    your Appx server,

       a) Examine the /etc/oratab file to find your Oracle SID

       b) Examine the /etc/oratab file to find your $ORACLE_HOME

       c) Make sure $ORACLE_HOME is defined in your start-appxd.sh 
          script

       d) Create an Oracle FMS group (type 5) and enter the Oracle SID
          in the server name field

 2) If you know your Oracle server is installed on a remote host,

       a) Examine the /etc/oratab file to find your $ORACLE_HOME.   (In 
          this case, $ORACLE_HOME will tell the OCI where to find config 
          files.)

       b) Examine the 'tnsnames.ora' file to find your remote server 
          name. 
       c) Make sure $ORACLE_HOME is defined in your start-appxd.sh 
          script.

       d) Create an Oracle FMS group (type 5) and enter the remote
          server name in the server name field.
         www.appx.com/assets/asp/dynamic_generator.asp?pageid=605

         www.appx.com/assets/asp/dynamic_generator.asp?pageid=682
      BEG READ 0AD PROCESS                HOLD 1 KEY IS  PROCESS KEY
      END READ 0AD PROCESS

 Waiting for lock held by APX in /usr/appx/data/00/SUR/Data/PROCESS.dat
 Waiting for lock held by session 9999 in /appx/data/00/SUR/Data/PROCESS.dat

 Windows - use SysInternals.com's Process Explorer utility:
           http://www.sysinternals.com ... look for "Process Explorer"

 AIX     - http://aixpdslib.seas.ucla.edu/packages/lsof.html
 HP/UX   - http://hpux.cs.utah.edu/hppd/hpux/Sysadmin/lsof-4.70
 Red Hat Linux - part of the lsof RPM package
 Solaris - use the fuser command instead of lsof

How can I easily reprint a file that's has been requeued (saved in the print
directory) without using the winprint from the dos prompt?  The file in
question is checks.  Once you print them you can't rerun the process.  
I cannot use the winprint command from dos because I need to grab the form 
file so it spaces everything correctly.

When you requeue an APPX report, it leaves the print file and a configuration 
file in the user's print directory after they've been submitted to the print 
spooler.

For example, when printing a System Administration list, the print file might  
be SYSADMI0 and the configuration file SYSADMI0.cfg

If you wanted to reprint this report, you might submit commands like the  
following:

If you are on Windows:

     cd  C:\appx\data\PRINT\USR
     C:\appx\data\winprint.exe  -config=SYSADMI0.cfg  SYSADMI0
or
     C:\appx\data\winprint.exe  -config SYSADMI0.cfg  SYSADMI0

The general form is:

     winprint.exe  -config=<config.file>  <print file>
or
     winprint.exe  -config <config.file>  <print file>

For those on Unix/Linux:

/usr/local/appx/data/appx_print -config=/usr/local/appx/data/PRINT/USR/SYSADMI0.cfg
/usr/local/appx/data/PRINT/USR/SYSADMI0

You can construct and issue shell (DOS) commands by means of the RUN command. 
You'll find documentation for it in the Designer Reference Manual, and at 
www.appx.com/pub/documents/HowTo/run.Windows.Functions.html 

The print file name can be found in --- PRINT FILE PATHNAME.  You'd be well
advised not to operate on the file pointed to by --- PRINT FILE PATHNAME, 
until after you've exited the OUTPUT process that generated the print file.  
This means passing the contents of --- PRINT FILE PATHNAME to a subsequent 
job step, possibly by means of a related or detached work field.
       Building Dynamic Index
       You are building a dynamic index for
       a possibly large number of records.
       This process may take a long time.
       Please CANCEL to stop building index.
       Press RETURN to continue.
        APPX_DYNAKEY_PROMPT=5000
        APPX_DISABLE_DYNAKEYS=yes
  C:\Documents and Settings\{yourWindowsID}\.appx\cache\

  C:\WINNT\.appx\cache\

  $HOME/.appx/cache/

Method #1:  Start > Settings > Control Panel > Administrative Tools >
                    Data Sources (ODBC) > Drivers Tab > Version

Method #2:  Windows Explorer > {your Windows Directory} > System32 >
                    AppxODBC.dll > Properties > Version Tab > "File
     IF  you are on 4.1:
     recover  FILE.bad.dat  FILE.dat > FILE.corrupted

     If you are on 4.2:
     appx -recover FILE.bad.dat FILE.dat > FILE.corrupted
Bruce Johnston Jan 14, '04:
FOR THOSE OF YOU ON WINDOWS, here're a few .bat files in a .zip to help you do this.

They assume that they and the recover.exe reside in D:\APPX\Tools and that D:\APPX\Data is the starting path for your .dat and .key files so you might have to edit them accordlingly.

One is standalone, rebuild.bat, and it is for doing the cmd line work on a single file.  It's syntax is
rebuild ver_or_db app datfilenamewithoutextension
No wildcards allowed for this one!

The other four are invoked in sequence rebuild1 ... rebuild4 with rebuild1 being invoked from the command line as
rebuild1 ver_or_db app datfilenamewithoutextension
but, in this case, all three parameters may contain dos wildcards
e.g.
rebuild1 01 T?? *
should run recover against all of the design files in the T-Apps, assuming no file locking issues.
and,
rebuild1 TST * C* would run recover againt the TST database for all files starting with "C" across all applications.

Hopefully, I'll be able to upload rebuildx.zip after completely this...
That didn't work so here're the .bat files:

rebuild.bat
>>>
d:
cd\appx\data
cd %1
cd %2
cd data
del %3.ke0
ren %3.key %3.ke0
del %3.bad
del %3.del
del %3.da0
ren %3.dat %3.da0
d:\appx\tools\recover %3.da0 %3.dat %3.del > %3.bad
cd..
cd..
cd..
<<<

rebuild1.bat
>>>
REM     Receives %1 = 1st level below APPXPATH (Company or Version)
REM              %2 = 2nd level below APPXPATH (Application)
REM              %3 = .DAT file spec WITHOUT the extension
REM     Wildcards permitted at all three levels.

REM     Note that the "/d" usage in the FOR commands implies
REM     that the command line extensions in NT server be supported.

REM     Make sure that "d:\appx\tools" is changed to match the path to
REM     you own .BAT files. AND RECOVER.exe

d:
cd\appx\data
for /d %%d IN (%1) DO CALL d:\appx\tools\REBUILD2.bat d:\appx\tools %%d %2 %3
<<<

rebuild2.bat
>>>
REM     REBUILD2.bat
REM     CALLed from REBUILD1.bat 
REM     Receives %1 = path to REBUILD3.bat and RECOVER.exe
REM              %2 = 1st level below APPXPATH (Company or Version)
REM              %3 = 2nd level below APPXPATH (Application)
REM              %4 = .DAT file spec WITHOUT the extension

cd .\%2
for /d %%d in (%3) do CALL %%1\REBUILD3.bat %1 %%d %4
REM     In case dir structure or wildcards were wacky
REM     Force a return to where REBUILD1.bat started us.
cd\appx\data
<<<

rebuild3.bat
>>>
REM     REBUILD3.bat
REM     CALLed from REBUILD2.bat 
REM     Receives %1 = path to REBUILD4.bat and RECOVER.exe
REM              %2 = 2nd level below APPXPATH (Application)
REM              %3 = .DAT file spec WITHOUT the extension
if not exist .\%2\data goto ENDBATCH

cd .\%2
cd .\data
for %%f in (%3.dat) do CALL %1\REBUILD4.bat %1 %%f
cd..
cd..

:ENDBATCH
<<<

rebuild4.bat
>>>
REM     REBUILD4.bat
REM     CALLed from REBUILD3.bat 
REM     Receives %1 = path to RECOVER.exe
REM              %2 = .DAT file spec
REM
REM     Thanks to Paul Peterson, (ppeterson@utahsbr.edu)
REM     I know that %~n2 returns the file name
REM     WITHOUT the extension which he learned from
REM     (the?) Windows NT Scripting Administrators Guide
REm             by William R. Stanek

del %~n2.ke0
ren %~n2.key %~n2.ke0
del %~n2.bad
del %~n2.del
del %~n2.da0
ren %~n2.dat %~n2.da0
%1\recover %~n2.da0 %~n2.dat %~n2.del > %~n2.bad
<<<
 a) Verify that the files are indeed OK.

 b) cd $APPXPATH/vv/aaa/ where "vv" is the version and
      "aaa" is the application id

 c) chmod 777 Resource

 d) chmod 777 Resource/*

 e) rm -f Em/*

 f) rm -f Dbg/*

 g) On your local client system, remove the ".appx" cache directory
    tree.  It should be in your home directory.  If you look at 
    home\appxlog.txt file in your client directory, it will 
    have a log line with the path to your local .appx cache directory.

 h) Check that the case of the filenames in the resource file exactly
    match the case of the filenames on disk.

 i) Try to load the screen again in the image editor

 j) If it still fails, email home\appxlog.txt as it exists 
    right after killing the client from a lockup, to techsupp@appx.com.

  If OS is set, then your operating system is NT, 2000, or XP

  If OS is not set then your operating system is 95/98/ME

  If OS=Windows_NT, and the variable "ProgramFiles" is set then you have
  an operating system that is 2000 or XP, else your operating system is   
  NT.
     Seq No  Field Name          Field Type Format
     ======= =================== ========== ======================
     100     VERSION SIZE        DOMAIN     S9(10)
     200     VERSION MAJOR       DOMAIN     S9(10)
     300     VERSION MINOR       DOMAIN     S9(10)
     400     VERSION BUILD       DOMAIN     S9(10)
     500     VERSION PLATFORM    DOMAIN     S9(10)
     600     VERSION CSD         ALPHA      X(128)
      SET      --- TEMP 80                    =      kernel32.dll,
      APPEND   --- TEMP 80                    0      GetVersionExA
      *
      SET      1EX VERSION SIZE               =      148
      PASS     1EX VERSION                    RECORD           SHARE? Y
      CALL     --- TEMP 80                    RESIDENT? N  END? N  FAIL 0
> # which appxps
/bin/appxps

> # cat /bin/appxps
#!/bin/sh
ps -axwo ruser,pid,ppid,c,stime,tty,time,args

> # appxps|grep appx
root     1573     1 0 Jan11 ?     00:00:00 /appx/tools/appxd -s=8066
root     1576     1 0 Jan11 ?     00:00:00 /appx/tools/appxd -s=8090
appx     1589     1 0 Jan11 ?     00:00:00 /appx/appx -l=/appx/license.log
nobody   1660  1573 0 Jan11 ?     00:00:00 /appx/data/../appx -f=4 -fms_server
al      11565  1576 0 Jan12 ?     00:00:01 /appx/data/../appx -f=4 -d=   
brenda  22224  1576 0 Jan13 ?     00:00:01 /appx/data/../appx -f=4 -d=   
al      24736  1576 0 Jan13 ?     00:00:10 /appx/data/../appx -f=4 -d=   
al       4786  1576 0 10:22 ?     00:00:04 /appx/data/../appx -f=4 -d=   
pat      6181  6180 0 12:42 pts/1 00:00:00 /bin/bash  /home/pat/.appx_profile
pat      6183  6181 0 12:42 pts/1 00:00:01 /appx/appx -d=CTS
root     6574  6522 0 13:17 pts/0 00:00:00 /bin/sh  /bin/appxps
root     6575  6522 0 13:17 pts/0 00:00:00 grep appx

> # 
          appx -l=logfile
               APPX_LS_DBG=0xFFFFFFFF
               APPX_LS_LOG={some.file.location.and.name}
 ftp://customerftp.appx.com/hostinfo/
          cd c:\appx\data\00\TAP\Portdata
          FOR %%f IN (*.) DO c:\appx\tools\appxutil -i=%%f 

   The name of an executable module is derived from the date that the PROCESS                                                                             
   record was added for that process.  If you happen to get two processes with 
   the same "date added", they'll have the same EM name and nasty things will 
   happen.  "Reset Process Date Add"  assigns a unique "date added" to every 
   process record.
   This resets the Date Compiled fields for all data Field and Domain  
   definitions in an application to NULL and also resets the internal Appx Area 
   Number for each field to zero.

   Resetting the compile date to null forces all fields and domains to 
   recompile.

   The Appx Area Number is how Appx locates data in memory.  We have had bugs in
   the past that caused two or more fields to have the same area number meaning 
   they shared the same memory space, which is a very bad thing.  Setting the 
   area number to zero for all fields forces appx to assign all new area numbers
   and thus fix the memory corruption problem.
   It deletes and then re-creates the given files.  
   When the data dictionary compiler compiles a dictionary, it writes records 
   into those four files.  When the process compiler compiles a process, it 
   reads from those files, not the FIELD and RECORD file.  So, initializing 
   those files is basically the same thing as deleting your data dictionary and 
   typing it all back in again - you end up with an uncompiled dictionary.

   Analyzes the source form of the data dictionary for errors and 
   inconsistencies and produces a more directly executable form (the compiled 
   form is stored in BITMAP, ELEMENT, FILE, and INITIAL).

   Restructure changes existing data records into a new form after you've 
   changed (and compiled) a data dictionary.

     The appx.stk dump, 
     The version# of APPX under which you are running, 
     The release level of your Operating System, 
     A brief description of what the error looks like from the operator's
     perspective, and a brief description of the Application Design elementes 
     in which the error occurred. 
     LogonUser() failed with 9999
 /usr/local/appx/appx -recover -c INDEXED.dat CONSEC.dat INDEXED.deleted
First, before you run asql.exe, set the expert mode environment variable as follows:

ASQL_EXPERT_MODE=1

1) Run asql and select the file that you wish to import the schema for.
2) Click on the "Show Script" button. The "create table" script should be displayed in the lower window.
3) Remove all of the comment lines from the script
4) Change field names to suit your purposes
5) Remove the last ";" from the very end of the script
6) Click on the "Try Again" button.
7) If "OK" is displayed, then everything probably worked as expected.
8) If there is an error, drop the table and try again.
9) WinSQL can be used to verify that the table, field names, and indexes were created as expected.

            APPX_LABEL_MEMORY=1

   Application Design > Utilities > Toolbox > Conversion 
   Utilities > Check for Duplicate ANO and EMs.
 1) Run:  
      Conversion Utilities > Reset Process Date Add Fields
      Conversion Utilities > Reset DD for full process

 3) Go into System Admin > Source File Management for your 
    application, initialize the 4 DD object files (BITMAP, 
    ELEMENT, FILE, INITIAL), and recompile the Data 
    Dictionary.

 4) Restructure your enduser datafiles.  
    (This shouldn't take long.)

 5) Delete your Application's EMs

          export APPX_TRAILER_COUNT=40

    http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_ts_8dbn.asp 

  $(host)         -  host name
  $(engine)       -  Appx engine version
  $(endian)       -  'intel' or 'risc'
  $(root)         -  $APPXPATH
  $(uid)          -  3-character Appx User ID
  $(user)         -  OS User ID
  $(pid)          -  OS Process ID
  $(ap)           -  File's application ID
  $(ver)          -  File's application Version
  $(db)           -  File's Database ID
  $(scope)        -  Process nesting level
  $(file)         -  8-character file name
  $(type)         -  "Data", "Struct", "Portdata", etc.
  $(anything-else)-  An environment variable

        $(root)/$(db)/$(ap)/$(type)/$(file)

        $(root)/$(ap)/$(db)/$(type)/$(file)

        /tmp/$(user)/$(type)/$(file)

 jdbc:odbc:appxodbc
 jdbc:odbc:appxodbc;UID=appx;PWD=password

        if the field is a key segment , Appx builds a CHAR(n) column
        if the field is less than 6 character long, Appx builds a CHAR(n) 
        otherwise, Appx builds a VARCHAR(n) column
        for CCYYMMDDhhmmss key segments, Appx builds a VARCHAR(14) column
        for CCYYMMDDhhmmss non-key fields, Appx builds a DATE column
        for all other date components,  Appx builds a VARCHAR(n) column
        if field length = 1, Appx builds a NUMBER( 3, 0 ) column
        if field length = 2, Appx builds a NUMBER( 5, 0 ) column
        if field length = 4, Appx builds a NUMBER( 10, 0 ) column
        Appx builds a NUMERIC( x, y ) column 

        http://support.microsoft.com/?kbid=899976

        http://troels.arvin.dk/db/rdbms

        http://troels.arvin.dk/db/rdbms/#cli
These should appear in 

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\<service name>\Config

TCPEnableKeepAlive Y

TCPKeepIdle 300

TCPKeepInterval 60

TCPKeepCount 8

Tthe values shown are the default values, those values are installed when you create a new service 
and they are also the values that we use if the entries are missing from the registry.

The AppxDSvc installer only writes a Config entry if it differs from the default value.  
That means that the installer won't write out entries for the TCPKeepXXX values, 
but AppxDSvc will pretend like those values are present (and set to their default values).

You can add the entries manually if, for some reason, you want to change the defaults.
Setting                 Argument        Default What it does
----------------------- --------------- ------- -----------------------------------------------
TCPEnableKeepAlive      true or false   true    Enable dead connection detection
TCPKeepIdle             (seconds)       300     Idle time before starting to send pings
TCPKeepInterval         (seconds)       60      Interval between keepalive pings
TCPKeepCount            (count)         8       Count of keepalive ping attempts before closing

The time before a server session closes would be the combination of all of these.  
Here is what happens.

After 300 seconds of idle time the server TCP stack will start trying to ping the client TCP stack.  
The server will make 8 attempts to ping the client and get a response before giving up and closing.  
It will wait for 60 seconds after each ping attempt for a reply before sending the next ping.

So in this case it will be 300 seconds + ( 8 * 60 seconds ) = 780 seconds = 13 minutes 
before the server session goes away.
appxd has environment variables for these settings as follows:

APPXD_DISABLE_KEEPALIVE set to anything will turn off the keepalive code.

APPXD_KEEPIDLE     = TCPKeepIdle
APPXD_KEEPINTERVAL = TCPKeepInterval
APPXD_KEEPCOUNT    = TCPKeepCount
        1) the windows event log
        2) a pipe
        3) a gzipped flat ascii file
        4) an AppxIO data file
        5) stdout
        6) a flat ascii file

         =>

        /usr/lib/libc.2 =>      /usr/lib/libc.2

        /usr/lib/libdld.2 =>    /usr/lib/libdld.2

        /usr/lib/libc.2 =>      /usr/lib/libc.2

        /usr/lib/libm.2 =>      /usr/lib/libm.2

        /usr/lib/libnss_dns.1 =>        /usr/lib/libnss_dns.1

        /usr/lib/libdld.2 =>    /usr/lib/libdld.2

        /usr/lib/libc.2 =>      /usr/lib/libc.2

        /usr/lib/libpthread.1 =>        /usr/lib/libpthread.1

        /usr/lib/librt.2 =>     /usr/lib/librt.2

        /usr/lib/libcl.2 =>     /usr/lib/libcl.2

        /usr/lib/libisamstub.1 =>       /usr/lib/libisamstub.1

        /usr/lib/libdld.2 =>    /usr/lib/libdld.2

     For details on reading the log, see http://board.appx.com/faq/cache/633.html 

     For details on setting the variable to control the contents of the log,  see http://board.appx.com/faq/cache/634.html
 00 - 0000072.0797031 0000000.0057123 05000
 01 - 0000076.0737460 0000000.0043817 10001
 02 - 0000000.0000000 0000000.0000000 00000
 03 - 0000000.0000000 0000000.0000000 00000
 04 - 0000000.0022587 0000000.0022573 00002
 05 - 0000000.0000000 0000000.0000000 00000
 06 - 0000026.0281965 0000000.0031189 05001
 07 - 0000002.0012514 0000000.0012999 15003
 08 - 0000000.0000000 0000000.0000000 00000
 09 - 0000000.0000000 0000000.0000000 00000  
 10 - 0000000.0017440 0000000.0017440 00001
 11 - 0000024.0951585 0000000.0022819 05000
        operation type
        cumulative time spent performing that operation for that table
        longest operation of that type for that table
        number of operations of that type for that table
        00 - Read operations
        01 - Readnext operations
        02 - Write operations
        03 - Rewrite operations
        04 - Open operations
        05 - Reread operations
        06 - Search operations
        07 - Release operations
        08 - Search by primary key operations
        09 - Search by alternate key(s) operations
        10 - Position to start of table operations
        11 - Search by row identifier operations
         00 - 0000072.0797031 0000000.0057123 05000
  As mentioned above, a Read is performed whenever Appx needs to retrieve
  a record by a specific key value.  A Read is accomplished by performing a
  Search followed by a Readnext, so you should have at least as many Searches
  and Readnexts as you have Reads.
  A Readnext is performed whenever Appx has established a Search position
  within a file and then needs to retrieve the record following that position.
  A Readnext will be performed for READNEXT, BEG/END READ, and READ statements
  as well as for most PCF operations.
  A Write operation is equivalent to a WRITE statement - it causes a row to be
  INSERTed into a table.
  A Rewrite operation is equivalent to a REWRITE statement - is causes an SQL
  UPDATE statement to be executed.
  This entry reflects the amount of time required to open a table.  It includes
  querying the RDBMS data dictionary and performing all internal bookkeeping.
  The time required for this operation is usually negligible.
  Since Sybase does not perform row-level locking, Appx must simulate locking
  outside of the Sybase server. The algorithm used to simulate locking requires
  reading every locked record twice: once to retrieve the key values and once
  to read the rest of the record.  A Reread operation reflects the second read.
  There should be one Reread operation for each record held.
  A Search operation is performed whenever Appx needs to position to a specific
  key value.  Searches are usually (but not always) performed by a Readnext
  operation and are usually part of a BEG AT or READ operation.  Search
  operations are further divided into "Search by primary key", "Search by
  alternate key(s)", "Position to start of table", and "Search by row dentifier
  operations".  In the above example, you can see that we performed 5001
  searches: 1 position to start-of-table and 5000 read by row-id's.
  A Release operation is performed whenever Appx releases a hold on a locked
  record.  Appx will try to release holds on records which were not locked -
  the overhead is negligible and does not cause any i/o.
  This a subdivision of the Search operation.  It reflects the number of
  Search operations which specify a primary key value.  In Sybase - primary
  keys are implemented as a clustered index.
  This a subdivision of the Search operation.  It reflects the number of
  Search operations which specify an alternate key value.

  This a subdivision of the Search operation.  It reflects the number of
  Search operations which position to the first row in an index (as opposed
  to a specific key value).
  This is a subdivision of the Search operation.  Whenever Appx reads a
  row from a table, it remembers the row-identifier (in the case of Sybase,
  the row-id is the primary key).  If Appx needs to reposition to that row,
  it will use the row-id.  An Appx query process works by recording the 
  row-id's of all records which meet the query constraints and then re-reading
  the results using the row-id's.   The above example was produced by selecting
  5000 out of 5000 records in a query process.
        1)  The amount of time spent on 00 (Read), 01 (Readnext), 02 (Write),
            03 (Rewrite), 05 (Reread), and 06 (Search) operations.
        2)  The number of operations performed against each file compared to
            the number of operations performed against the PCF.
The APPX_DBG_CODE environment variable controls the amount of information written to the APPX_SQL_CMD log file.  APPX_DBG_CODE is a 32-bit bit mask - if a bit is on, the corresponding information will be logged.

Here are the current (01/22/98) bit definitions:

0x00000001 -    Log all generated SQL commands

0x00000002 -    Log status codes returned from server (*)

0x00000004 -    Log all fetch attempts (*)

0x00000008 -    Log all engine level operations (*)

0x00000010 -    Log all connection-related operations (*)

0x00000020 -    Log binding summary (*)

0x00000040 -    Log binding details (*)

0x00000080 -    Log column/field mappings

0x00000100 -    Enable server logging mechanism (Oracle only)

0x00000200 -    Enable result (null/non-null) logging (*)

0x00000400 -    Log negotiations for server options (such as packet size)

0x00000800 -    Log all records returned from server

0x00001000 -    Currently undefined

0x00002000 -    Log proxy locking operations (Sybase/ODBC only)

0x00004000 -    Time individual operations (use 0x10000 instead)

0x00008000 -    Enable server-side statistics (if capable)

0x00010000 -    Gather per-table timing statistics

0x00020000 -    Enable "show plan" feature on server, generates voluminous logs

0x08000000 -    Write server-based log to "/tmp/syblog" (Sybase only)

0xFFFFFFFF -    Logging all activity

Definitions marked with (*) are for internal debugging purposes only - they 
provide very little useful information.
Information regarding Language Translation and Language Translation Manual is 
available on our website:

http://www.appx.com/assets/asp/dynamic_generator.asp?pageid=558
    -form_id="U.S. standard fanfold"
    Why are my labels in an output PDF report being truncated?
Look for the following section in appx_print.  Remove or comment it out.
If you are doing client-side printing, appx_print will be in the client
install directory.  Otherwise, look for it in the $APPXPATH directory on
the server.

This is only for non-windows operating systems. Windows client and server
systems do not use mpage or appx_print.

#
# default format if one wasn't specified
#
if [ "$FORMAT" = "" ]
then
 FORMAT="MPAGE"
fi

    FMS Path:               R:\APPX\data
       (where R is the shared drive and path to the network Appx installation) 

    FMS Group Attributes:   EM=C:\APPX\local_data
 ---
 ---
 ---
Example where:

<dir>=c:\appxnet
<hostname>=myappxserver
<port>=8060
<userid>=joe
<password>=please

set APPXPATH=c:\appxnet
set APPX_DATA_SERVER=myappxserver:8060
set APPX_UID=joe:please
c:\appxnet\appx.exe
  # This file is used by ORACLE utilities.  It is created by root.sh
  # and updated by the Database Configuration Assistant when creating
  # a database.
  #
  # A colon, ':', is used as the field terminator.  A new line terminates
  # the entry.  Lines beginning with a pound sign, '#', are comments.
  #
  # Entries are of the form:
  #   $ORACLE_SID:$ORACLE_HOME:<N|Y>:
  #
  # The first and second fields are the system identifier and home
  # directory of the database respectively.  The third filed indicates
  # to the dbstart utility that the database should , "Y", or should not,
  # "N", be brought up at system boot time. 
  #
  # Multiple entries with the same $ORACLE_SID are not allowed.

  *:/opt/oracle/product/9.2.0:N

  oracle:/opt/oracle/product/9.2.0:N
  ORACLE.INTERNAL.APPX.COM =
    (DESCRIPTION =
      (ADDRESS_LIST =
        (ADDRESS = (PROTOCOL = TCP)(HOST = badger.appx.com)(PORT = 1521))
      )
      (CONNECT_DATA =
        (SERVER = DEDICATED)
        (SERVICE_NAME = oracle)
      )
    )

   a) Examine the /etc/oratab file to find your Oracle SID

   b) Examine the /etc/oratab file to find your $ORACLE_HOME

   c) Make sure $ORACLE_HOME is defined in your start-appxd.sh script

   d) Create an Oracle FMS group (type 5) and enter the Oracle SID
      in the server name field 

   a) Examine the /etc/oratab file to find your $ORACLE_HOME.   (In this
      case, $ORACLE_HOME will tell the OCI where to find config files.)

   b) Examine the 'tnsnames.ora' file to find your remote server name.

   c) Make sure $ORACLE_HOME is defined in your start-appxd.sh script.

   d) Create an Oracle FMS group (type 5) and enter the remote server
      name in the server name field.

  http://www.appx.com/assets/asp/dynamic_generator.asp?pageid=605
  http://www.appx.com/assets/asp/dynamic_generator.asp?pageid=682

        http://support.microsoft.com/support/kb/articles/q148/3/67.asp 
        NOTE ABOUT URLs:  Microsoft periodically rearranges its web
        site, so the above URL may or may not be valid.  If you can't
        find it, use the "Search" option on the MS web site, instructing
        it to look in whatever choice includes the "Knowledge Base".
        Specify "Qnnnnnn" as what to look for, where nnnnnn is the number
        between the "q" and the ".asp".  For example, in the above, it
        would be Q148367.  That should enable you to locate the article.
     http://support.microsoft.com/support/kb/articles/q142/6/76.asp 
        NOTE ABOUT URL's:  Microsoft periodically rearranges its web
        site, so the above URL may or may not be valid.  If you can't
        find it, use the "Search" option on the MS web site, instructing
        it to look in whatever choice includes the "Knowledge Base".
        Specify "Qnnnnnn" as what to look for, where nnnnnn is the number
        between the "q" and the ".asp".  For example, in the above, it
        would be Q148367.  That should enable you to locate the article.
       - Act as part of the Operating System
       - Replace a process-level token
       - Increase quota
       - Logon as a service (if it's not already set)
          APPX_SERVER    - set to full path of appx.exe
          APPX_KEYMAP    - set to "Windows"
          APPXPATH       - set to your APPX data directory
     APPX_SERVER - Full path to the appx.exe on the server.  Make sure
                   that you reference a drive that is available from
                   the server, not a network drive that is only visible
                   from clients
     APPX_KEYMAP - Normally set to "Windows", but you can set it to
                   a different name if you wish to customize the
                   keymap
     APPXPATH    - Full path to your APPX data directory
              C:> ipconfig /all
         HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinAppxD

        - your replacement print script must be in the APPXPATH directory
        - you must set APPX_PRT_SCRIPT to the file name, not including
          any directory or drive letter information in front of it (for
          example, you might set APPX_PRT_SCRIPT=myprint.exe)
        - APPX_PRT_SCRIPT must be set ON THE SERVER (not the client;
          remember, when connecting to APPX Presentation Server, the
          SERVER controls the printing), along with APPXPATH and the
          other standard variables.  Generally this is done from
          Control Panel / System / User Environment.  Remember to
          reboot after you change this.
        c:\appx> winappxd -s=8060

                  4-users  16usrs  32users  64users
    nfile            1000    4000     8000    16000
    nflocks           500    4000     8000    16000
    ninode            750    3000     6000    12000
    maxfiles          512    2048     4096     8192
    maxfiles lim     1024    2048     4096     8192
    semmnu             30      48       96      192
    nfile        - 1 for each file opened by each user on the system
    nflocks      - nfile + 1 for each locked record on the system
    maxfiles     - 1 for each file opened by a given user
    semmnu       - 1 for each APPX session (user or background)

        (a)     Run �Create Files�

        (b)     Run �Convert From Pre 4.1 to 4.1

        (c)     Run �Sync Widget Elements�

        (d)     Run "Create Executable Modules"