Difference: 0LASubrFileSetSpecs (2 vs. 3)

Revision 32019-10-10 - AlKalter

Line: 1 to 1
 
META TOPICPARENT name="FullAPIList"

.FILE SET SPECS

Line: 51 to 51
  All fields in --- FMS are optional. If not supplied, the original value (if any) remains in place. Fields that are not part of a given FMS Type will be ignored (ie, setting a Port number on an APPX/IO file). If you change the FMS type of a file, all previous settings will be cleared and only the settings you supply will be used.
Changed:
<
<		The FMS USE DB is a special case (corresponds to the 'Use DB' column in Data File Management). If this is set to a valid Database, then all previous file specifications will be cleared and the file will be set to the FMS Type of the file in the FMS USE DB. If this file cannot be found, it will default to a Type '1'. There is no point in setting any other FMS attribute in this case, since APPX will use the ones on the specified DB.
>
>		The FMS DB USE is a special case (corresponds to the 'Use DB' column in Data File Management). If this is set to a valid Database, then all previous file specifications will be cleared and the file will be set to the FMS Type of the file in the FMS DB USE. If this file cannot be found, it will default to a Type '1'. There is no point in setting any other FMS attribute in this case, since APPX will use the ones on the specified DB.
 
Changed:
<
<		The following is a list of what fields are applicable to each FMS type when you are not setting FMS USE DB.
>
>		The following is a list of what fields are applicable to each FMS type when you are not setting FMS DB USE.
 

APPX/IO

FMS FMS - Set to '1' to designate the file as an APPX/IO file, or '9' for a large file (>4g)

Line: 67 to 67
 FMS FMS TRACK LCK - The 'Track Locks' flag

FMS FMS LOGPROF - The name of a valid Log Profile

Added:
>
>		 FMS DB USE - A valid Database, from which data will be used. NOTE: If set, then all previous file specifications will be cleared and the file will be set to the FMS Type of the file in the FMS DB USE. All other specifications in the FMS file will be ignored.
 

Accucobol Vision

FMS FMS - Set to '2' to designate the file as an Accucobol Vision ISAM file.

Line: 80 to 82
 FMS FMS CTL - A free format string. This has no meaning to APPX and is intended to pass any parameters required by the Accucobol Vision interface.

FMS FMS LOGPROF - The name of a valid Log Profile

Added:
>
>		 FMS DB USE - A valid Database, from which data will be used. NOTE: If set, then all previous file specifications will be cleared and the file will be set to the FMS Type of the file in the FMS DB USE. All other specifications in the FMS file will be ignored.
 

Informix C-ISAM

FMS FMS - Set to '3' to designate the file as an Informix C-ISAM file.

Line: 93 to 97
 FMS FMS CTL - A free format string. This has no meaning to APPX and is intended to pass any parameters required by the Informix C-ISAM interface.

FMS FMS LOGPROF - The name of a valid Log Profile

Added:
>
>		 FMS DB USE - A valid Database, from which data will be used. NOTE: If set, then all previous file specifications will be cleared and the file will be set to the FMS Type of the file in the FMS DB USE. All other specifications in the FMS file will be ignored.
 

Oracle

FMS FMS - Set to '5' to designate the file as an Oracle file.

Line: 136 to 142
 FMS FMS SUPR NULL - Determines whether or not to disable the null numeric feature inherent in the database; set to "Y" if you want to be consistent with APPXIO behavior which does not have this capability (a zero entry cannot be distinguished from a null value in APPXIO)

FMS FMS FORCE VAR - Set to "Y" to force Appx to use VARCHAR for all alphanumeric fields. If you set this field to "N", Appx will use CHAR for alpha key columns and alpha columns shorter than six bytes.

Added:
>
>		 FMS DB USE - A valid Database, from which data will be used. NOTE: If set, then all previous file specifications will be cleared and the file will be set to the FMS Type of the file in the FMS DB USE. All other specifications in the FMS file will be ignored.
 

ODBC / DB2

FMS FMS - Set to '6' to designate the file as a file in an ODBC compliant database (ie, SQL Server, MySQL, etc) or 8 to designate a file in DB/2.

Line: 157 to 165
 FMS FMS SUPR NULL - Determines whether or not to disable the null numeric feature inherent in the database; set to "Y" if you want to be consistent with APPXIO behavior which does not have this capability (a zero entry cannot be distinguished from a null value in APPXIO)

FMS FMS RD UNCOMT - This determines whether or not to read a record with an update pending which has not yet been committed. If set to "Y", Appx will read the uncommitted changes. This more closely emulates AppxIO behaviour. If set to "N", Appx will wait for the data to be committed or rolled back.

Added:
>
>		 FMS DB USE - A valid Database, from which data will be used. NOTE: If set, then all previous file specifications will be cleared and the file will be set to the FMS Type of the file in the FMS DB USE. All other specifications in the FMS file will be ignored.
 

APPX/NET

FMS FMS - Set to '7' to designate the file as an APPX/NET file

Line: 172 to 182
 FMS FMS PORT - The port number on the indicated server

FMS FMS LOGPROF - The name of a valid Log Profile

Added:
>
>		 FMS DB USE - A valid Database, from which data will be used. NOTE: If set, then all previous file specifications will be cleared and the file will be set to the FMS Type of the file in the FMS DB USE. All other specifications in the FMS file will be ignored.
 

Comments:

Read what other users have said about this page or add your own comments.

View topic | History: r4 < r3 < r2 < r1 | More topic actions...
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback