On the Network and DOS based versions of Unibase by DMAC, a long drun may be gracefully terminated by pressing the {SCROLL LOCK} key. If you forget to turn off the {SCROLL LOCK} key, the next time you execute a drun, you will get the message 'Terminating at Operator Request'.

Return to Questions
 

Yes, if output is done by the backup server. The environment variable ETDUAL2 has been added. When ETDUAL2 points to the location of the files on the other server, then Unibase by DMAC will simultaneously mark files on the primary and backup as having been output.  On a Novell network, it usually requires attaching to the other server and mapping a drive letter to the other system. 

Example: map p:=server1_name\sys:\unibase\files
Then set ETDUAL2=p: 

On a UNIX system, doing this will usually require setting ETDUAL2 to the full path of the files on the other server including the server name. 

Set ETDUAL2=server_name:user/unibase/files

Return to Questions
 

The environment variable TABSZ may be used to set the width of the tab stops in ez_edit.

Return to Questions
 

Yes, ez_edit will now handle very large files and a counter has been added to show that it is reading in a large file.

Return to Questions
 

Yes, the high and low ranges in the check box edit portion of the record format generator will now accept negative numbers provided the field type is numeric.

Return to Questions
 

The environment variable TATT (Tag Screen ATTribute) is used to set the non-gui default tag screen attribute used in the "paint the screen" portion of the record format generator. TATT=A, B, C, D, or E respectively gives normal characters, highlighted characters, underlined characters, blinking characters, or reverse characters for the tag display.

Return to Questions
 

The environment variable FATT (Field Screen ATTribute) is used to set the default field screen attribute used in the "paint the screen" portion of the record format generator. FATT=A, B, C, D, or E respectively gives a normal underline, a highlighted underline, an "underlined" underline (which looks like a solid line), a blinking underline, or a reverse underline for the field display.

Return to Questions
 

Yes. Environment variable UBDATE alters the order of the month, day, and year on the login menu, when displaying file information, when displaying status information and when displaying the system date. UBDATE set to 0 gives mmddyy. UBDATE set to 1 gives ddmmyy. UBDATE set to 2 gives yymmdd.

Return to Questions
 

Yes. The path description for devices in the device table may now include the control function <OPID>, any global variable ($var01-$var99), or any environment variable (%variable%). If global variables are going to be used, the environment variable UBPARENT=Y should be set to ensure that global variables retain their values. CAUTION. Any programs that use global variables should be SURE to initialize them properly as global variables retain values unless erased by a parent program.

Return to Questions
 

Yes. Color choices from the Operator Log-In can now be aborted by keying 1 space 1 space 1 space 1 space 1 space {FLD REL}.

Return to Questions
 

All hex characters in the range of 00 to fd may be output using the control functions <hex nn> when nn is the hex character you wish to output. The hex characters in the range of fc to ff may be output by setting the environment variable ALLHEX=Y in the Unibase.ini file in the Unibase\bin directory. However, fc through ff may not be used with spooled devices.

Return to Questions
 

Unibase by DMAC can output an unlimited number of files in the DOS/Novell version.

Return to Questions
 

Yes, starting with Unibase version 7.4, it is compatible with all Windows versions up to Windows 98, Release 2.

Return to Questions
 

Yes, by setting the environment variable UBSESN. Each session of Unibase will require a DIFFERENT (UBSESN) session number. Bat files should be created with different session numbers (up to 50). The format is UBSESN=n where n is a number from 1 to 50. The config.sys file needs to be modified to increase the number of files and buffers allowed so that it will accommodate multiple sessions of Unibase.

Return to Questions
 

If you are going to use sessions, then operators in data entry should be instructed to key {RCD} {S} before switching to another session. This command, which is normally used to suspend the clock, also tells Unibase to close any files that data entry might have open/locked. When the operator returns to the session, simply pressing any key will resume operations for the session.

Return to Questions
 

Beginning with version 7.2, the keyboard program defaults to the newer extended keyboards and expects KBEXT=Y to be set in the Unibase.ini file in the Unibase\bin directory. To use an old keyboard, you must remove KBEXT=Y from the setup.bat file in the Unibase\bin directory and map the arrow keys on the numeric keypad accordingly. Even if you have a separate arrow keypad, it will be inoperable unless you have an extended keyboard.

Return to Questions
 

Yes, if UBRSET=Y is in the Unibase.ini file in the Unibase\bin directory, then the {FIELD REL} key no longer resets an error message. Only the designated {RESET} key will do so.

Return to Questions
 

Yes. If KEYBUK=Y is set in the Unibase.ini file in the Unibase\bin directory, then Unibase accesses SHOWKEYU instead of SHOWKEY and CHNGKEYU instead of CHANGKEY. These display the keyboard layout from the United Kingdom. Also, there is a file KEYBOARD.UK in the misc directory, which when renamed to KEYBOARD, displays the characters on a UK keyboard for the typewriter overlay.

Return to Questions
 

Yes, Unibase will support a Computer Logics Nine Track tape drive controller. The environment variable UBTPCL=Y must be set in the Unibase.ini file in the Unibase\bin directory to use this controller and TDRIVER.EXE, OUTRIGHT.CFG, LCA.BMD, and LCA.SGL files from the Computer Logics programs must be in the Unibase bin directory. Unibase by DMAC will load TDRIVER as needed. (Computer Logic now calls its program API.EXE and this program must be renamed to TDRIVER.EXE before Unibase can use it. This works in DOS only.

Return to Questions
 

Yes, packed decimal output to tape is available. You MUST use the EBCDIC codeset when you output and then you MUST use the ASCII mode when making the tape. Also, for every packed decimal field, you must allow two extra bytes in the record length in the standard job. The two extra bytes are used by Unibase and are not output.

Return to Questions
 

Yes. If NOCHBKFL=Y is set in the Unibase.ini file in the Unibase\bin directory, then a keyer cannot character back into another field. Once character back reaches the beginning of a field, then it no longer has an effect. The keyer MUST use field back to get to the prior field.

Return to Questions
 

Yes. When FLDCORBG=Y and RCDCORBG=Y are set in the Unibase.ini file in the Unibase\bin directory, doing a {FLD} {CORR} / {RCD} {CORR} will always go to the beginning of the field/record.

Return to Questions
 

Yes, this is done by pressing {RCD}{G} or by mapping a key to "BE " which stands for bypass error. {RCD}{F} also works as a way to flag an error.

Return to Questions
 

Yes. See Manual 4, Appendix D, Page 23.

Return to Questions
 

Yes. With ETSWAP you can specify any pathname (not over 21 characters) in the Unibase.ini file in the Unibase\bin directory.

Return to Questions
 

Yes, as long as UBKEYR1=Y is set in the Unibase.ini file in the Unibase\bin directory. This allows the top row of keys to function independently of the data type (A,N,L,U,M,B,T) when the operator is in TYP (non 029) mode.

Return to Questions

Yes, by setting the environment variable UBNMULG=Y in the Unibase.ini file in the Unibase\bin directory.

Return to Questions
 

Yes, the "Purge Deleted Records" function under Utilities will handle files specified with a wild card.

Return to Questions
 

Yes. The verbs "setupper", "setnormal", "setlower" and "setuplower" (sentence case), control the case of records output from an output program.

Return to Questions
 

Yes, global variables may be used in the define file statements.

Return to Questions
 

Yes, global variables may be used as datafile and index names in open statements.

Return to Questions
 

Yes. The "equate" verb tells Unibase to declare a variable ("variable") so that every time it appears in this program, it is read as the source. It can also be used for constants in the program. For instance, it is useful for equating names to field numbers or foreign names to Unibase verbs.

Return to Questions
 

Yes, if you set environment variable UBOVNR=Y in the Unibase.ini file in the Unibase\bin directory, it will NOT release the field in data entry when the oversign key is used.

Return to Questions
 

The environment variable DMACI (which must be set in the Unibase.ini file in the Unibase\bin directory) for image entry has a sub-variable V:, which refers to the VGA mode to be used. V:LOW is mode: 12h, displays 640 pixels x 480 pixels x 16 colors for an image. V:HIGH is mode: 102h, displays 800 x 600 pixels x 16 colors. V:HIGH1 is mode 104h, displays 1024 x 768 pixels x 16 colors. V:SUPER is mode 106h, displays 1280 x 1024 pixels x 16 colors. Remember that as more of the image is displayed, the smaller the text/picture becomes. If the monitor cannot display the specified resolution, Unibase by DMAC will drop back to a display that the monitor can handle.

Return to Questions
 

Yes, by using the code {0}|af, where {0} refers to the image in the work file record and |af indicates to convert it to an ASCII file that represents a binary file.

Return to Questions
 

Yes, by using the control function <ilist 0,cntr>.

Return to Questions
 

Yes, by using the control function <isource 0>.

Return to Questions
 

By using control function <ipathidx 0>. It gives the number of the path definition in the imgpath.idx file used with the current record of the current work file.

Return to Questions
 

By using control function <ipath 0>. It gives the current record's image path.

Return to Questions
 

By using control function <iname 0>. It gives the name of the image being used with the current record of the current work file, including the first directory.

Return to Questions
 

A.

You need to use the control function <ientry 0>. It tells if images are used in the current workfile. If <ientry 0> is 0, then the workfile does NOT use images. If it is 1, then the workfile USES images.

Return to Questions
 

Yes, by using the control function <icount 0>. It gives the number of images in the current work file.

Return to Questions

By using the control function <vtime 0>, it displays the elapsed verify time as hhmmss.

Return to Questions
 

The control function <voper 0> contains the name of the most recent operator to access the current workfile in verify mode.

Return to Questions
 

The control function <recfmts 0> returns a 2 digit number of the record formats in the Standard Job used to create the file. Also, you can open the Standard Job and view the Record Format list.

Return to Questions
 

Yes, by using the control function <outdev 0;1>. If the current workfile has been output, this is the name of the output device where n=1 is the most recent outdev. Also found under file function in display file info.

Return to Questions
 

Yes, by using the control function <lmode 0>. It is a one letter code for last mode of access. The codes are 0-entry, resume or update; 1-verify; 2-examine; 3-correct. Another way is to use a file edit, using the control function <mode>.

Return to Questions
 

Yes, by using the control function <etime 0>. It displays the elapsed entry time as hhmmss.

Return to Questions
 

Yes, by using the control function <eoper 0>. It contains the name of the most recent operator to access the current work file in entry mode.

Return to Questions
 

Yes, the control function <cdate 0> gives the creation date for the current workfile.

Return to Questions
 

The control function <accum 0;xx> gives the current value of accumulator xx for the current workfile.

Return to Questions
 

Yes, if the environment variable UBTYPW=Y is set in the Unibase.ini file in the Unibase\bin directory, and only if the operator is also in typewriter mode.

Return to Questions
 

Yes, but it must be done from the DOS prompt. The syntax is: ubupgvar nn "data"nn is the global variable number and the data to be moved into it is in DOUBLE quotes. This program allows you to initialize or change global variables by system calls to a .bat file.

Return to Questions
 

Yes, using the F: parameter in the environment variable DMACI (which is used for imaging data entry only and must be set in the Unibase.ini file in the Unibase\bin directory). F:SMALL will use 8x8 pixel characters in the Unibase screen in image entry. F:MED will use 8x14 pixel characters. F:BIG will use 8x16 pixel characters. F:BIG1 will use 10x18 pixel characters. F:BIG2 will use 12x30 pixel characters. This parameter does NOT affect the image display portion of image entry. In order to avoid wrapping the screen display around on top of itself, parameter F:BIG1 is meant to be used with V:HIGH1 or SUPER and parameter F:BIG2 is meant to be used with V:SUPER.

Return to Questions
 

Set the environment variables UBMXX and UBMXY in the Unibase.ini file in the Unibase\bin directory. Unibase Image Entry allocates memory to handle approximately an 8 1/2" x 11" page image. This is an image width and length of about 2550 by 3300. If your image width and/or length exceed these defaults, use UBMXX and UBMXY to set larger sizes so Unibase knows to allocate more memory for the image.

Return to Questions
 

No, if environment variable UBDZF=Y is set in the Unibase.ini file in the Unibase\bin directory, zero length files will not stop with an error message if they are being processed, they will simply be bypassed. They will also be deleted like regular files.

Return to Questions
 

Yes, by setting environment variable UBDRSZ in the Unibase.ini file in the Unibase\bin directory. If the environment variable is set to a number such as UBDRSZ=4096, then that number is used as the default size. If that number is NOT set, then the default is 80 characters.

Return to Questions
 

Yes, set the environment variable UBPOS1=Y in the Unibase.ini file in the Unibase\bin directory. It will refresh the screen when a position statement is executed in both image entry, as well as data entry as long as there is not a program that uses 'show' statements to display information. If there is a 'show' statement, this data will not be erased whenever a position statement is executed.

Return to Questions
 

Yes, by using the verbs "search" and "searchf". The verb "search" will report occurrences of the string across field boundaries. The verb "searchf" restricts the search to occurrences within a field.

Return to Questions
 

Yes, with the <date4> control function. It returns an eight digit result in the form mmddyyyy. The environment variable UBDATE also affects <date4>.

Return to Questions
 

Yes. Put UBFMTL=Y in the Unibase.ini file in the Unibase\bin directory. You must also assign the format name in every field edit program.

Return to Questions
 

Put UBNOFF=Y in the Unibase.ini file in the Unibase\bin directory. When it is set to Y, output sent to LANPRx devices will NOT perform a top of form at the end of the output.

Return to Questions
 

Yes, by placing the environment variable UBTAB in the Unibase.ini in the Unibase\bin directory. When it is set to Y, tabbing to a field NOT on the screen in data entry will position the "tabbed to" field on the last line of the screen instead of the first line of the screen.

Return to Questions
 

Yes. You need to change your Unibase.ini in your Unibase\bin directory to reflect UBDD=Y. When it is set to that, a change made to a duplicating field while in verify will be carried forward through all succeeding records, even those with a different format number, where the field has been marked as record-to-record dupe and the contents of the succeeding fields were the same as the original field that was changed.

Return to Questions
 

Yes, by setting the environment variable UBIDX