Cory Gaw

Here is a listing of the SYSF commands that i currently have documented. I know there are a couple more that i'm researching, but at least this is a start!

1. To create a new file:

SYSF( &#@CREATE, $file_name, key_length, record_length )

Remember…. if you’re creating an ASCII file, the key length is zero


2. To create a new file in Btrieve:

SYSF(&#@CREATE,{filename},&#@BTRV,{record_length},'{key_length}@1')
where
{filename} is the physical file you want to create,
{record_length} is the record length displayed in @F
{key_length} is the key length displayed in @F

You need to use this form of the command because B-Trieve supports multiple indexes per file, so you need to specify where the primary key index lives (which is the {key_length}@1 bit)


3. To delete an existing file:

SYSF( &#@DELETE, $file_name )


4. To Check if file currently exists:

SYSF( &#@CHKFILE , $file_name , #A )

#A is “0” if file exists, or “1” if it does not exist


5. To rename an existing file:

SYSF(&#@RENAME,$FROMFILE,$TOFILE)


6. To retrieve system information from @SYSLOOK:
SYSF(9,,#VAR1,$VAR1,$VAR2,$VAR3,$VAR4,$VAR5,$VAR6)

#VAR1 = PRO-IV Version
$VAR1 = PRO-IV Release No.
$VAR2 = Release Date
$VAR3 = Customer Name
$VAR4 = Unknown
$VAR5 = Serial Number
$VAR6 = Enabled Options

7. To redraws the boarder around the current window. (Not too usefull!!!)

SYSF(17)


8. To retrieve the current PID status:

SYSF(21,$PID,#RESULT)

0 = no such PID, 1 = PID exists.


9. Get unix environment var $ENV and return in $RESULT

SYSF(22,$ENV,$RESULT)

Scott.

Sorry, but as we discussed this afternoon, i was mistaken. Support for 9i on v6.1 sp4 is restricted to Solaris. HPUX and other OS have not yet been certified.
My bad.

Gregg! I knew i could feel my ears burning for a reason.
Well, i don't use the file lock logic within SL, but i'll give you my understanding of the functionality.

If you're using it in a type 'U' or 'R' function, SL's not going to exit that logic ID and any FLD(xxx) or DSEL logic will be ignored unless you've added the SUPPRESS_RETRY(). If you do this, and don't specify a fld, it'll just drop out to the rtn_fld. You can track the number of times SL attempts to access the table with the @RETRYCOUNT and then issue the suppress once you're ready to give up, and fall out to your error routine.

Enabling 'LOCKED_ROWS_RETURNED' to the environment file, results in the 'NO WAIT' keyword being added to the sql select statement, thereby enabling Oracle to proceed.
If you suppress_retry in an 'S' function, it should attempt the write, and then release the lock, returning you to FLD for a new value. However, if FLD is a display only, it will loop again for retry.
If you're on a syspass in a paging screen when the lock hits, it should drop you out to the SEQ (first field, right?)
Now, my understanding of the processing is that you will not require 'lock logic' for all tables, as a result of enabling the 'locked rows returned' environment variable. SL's default logic should manage this. For the official documentation on this functionality, please refer to PRO-IV logic documentation for 'default behaviour' in the lock read access logic 'Using Logic, Chapter 2.
I hope this is helpful.

Scott.
With the current release of Glovia.com (v6.1 sp4), Oracle 8i & 9i are supported products on HPUX-11, PRO-IV v4.6r500. I'm not aware of any technical limitations. You can find the matrix supporting this on the glovia.com website.