Click above to get retro games delivered to your door ever month!

   This category groups the utility functions of AS/400

   These functions are available in the dBsee for AS400 version.

   NOTE for the utilize of dBsee for AS/400

   Limitation

   There are the following limitations of the use of database on AS400.

   1) It's not possible to create index on substring of fields
   2) It's not possible to have more than 5 active PATH on AS/400
   3) It's not possible to use Clipper 5.3.

   The functionality NOT available :

   1) The /UPD parameter on AS/400 database

   DUAL Executable

   Is possible to create a DUAL executable file that can be executed with
   AS/400 database or with PC database.

   The DUAL executable file can be created in the following way:

   1) Create an executable file in the AS/400 version. For each
      database you must define the WIN400 RDD.

   2) In the startup object, select the * #COD OBEXE0 injection
      point and insert the control on the type of the desired
      executing:

      LOCAL lWin400 := .F.
      lWin400 := dfYesNo("Executing on AS/400")

    3) At this point, the lWin400 is .T. if the executable
       work on AS/400 while is .F. if the executable work on PC.
       In the above injection point insert the code:

      * #COD OBEXE0
      LOCAL lWin400 := .F.
      lWin400 := dfYesNo("Executing on AS/400")

      dfSet( AI_AS400INIT, lWin400 )
      IF lWin400
         // Chang the RDD of all file that work on AS/400
         ddCngRdd( "Cli", "WIN400" )
         ....
      ELSE
         // Chang the RDD of all file that work on PC
         ddCngRdd( "Cli", "DBFNTX" )
         ....
      ENDIF
      dbCfgClose( "DBDD" )

      // At this point the system know if the AS/400 must be
      // initializating and where are the databases

      * #END

   4) If you respond Yes, the system work on AS/400 otherwise on PC.


   Optimization and useful adives

   1) You must have the dBsee4AS.obj file, otherwise the dBsee
      can't generate the AS/400 applications.

   2) I advise you to open the AS/400 databases at the beginning of
      the program with the dfASOpenFile( aFile ) function. This
      function must be inserted in the first injection point of the
      DBF() method of the menu.
      Generally (if the start object is named menu) this function is
      named MENUDBF() and the injection point is:


      * #COD OBDBF0 * #END //  Open the databases

      After the modification you must have the follow:

      * #COD OBDBF0
      dfASOpenFile( aFile )
      * #END //  Open the databases

      Caution

      The dfASOpenFile() open only the AS/400 databases.

   3) I advise you to delete the Reindex menu label as since on AS/400
      have not sense.

   4) To change the RDD of the table files and the password file, for
      making them work on the AS/400, you must insert in the first
      injection point of the menu the following code:

      * #COD OBEXE0
      dfLoginOnAS( .T. )
      dfTabOnAS( .T. )
      * #END //

   5) The PATH must be created in different mode.

      Path PC     = C:\DISK1\PROVA\
      Path AS/400 = PROVA:

      PIPPO is the AS/400 library that contain a HOOK configuration.

   6) dBsee allows to create databases and indexes in automatic way
      This operation require most CPU operation. I advise you to
      transfer the databases on AS/400 with HOOK.

   7) If you set a PATH in the application, this definition obtains
      a higher priority with respect to the DOS environment variable.

   8) The dfSet( AI_AS400INIT, .F. ) function allows to not
      connect the application with AS/400.

      Insert the function in the following point:

      * #COD OBEXE0
      dfSet( AI_AS400INIT, .F. )
      * #END //

   9) You can't use WIN400 as a default RDD of the application, but
      only as RDD on single file.