Suprtool provides fast access to your data on the HP e3000. With Suprtool, you can perform many necessary DP functions easily, with just a few simple commands. At Robelle we are constantly working on your enhancement requests so that we can include them every year when we release an updated version of Suprtool.

Highlights in Suprtool 5.5

· Set XLTRIM On now tells Suprtool to close a file and release the disc space between EOF and the Flimit.

· STExport's Escape command has been re-engineered to fix some corner cases that didn't work previously.

· Due to an issue with Btrees, Suprtool would incorrectly select records when doing an update or delete, and if using chain with a btree index on a master dataset.

· The $edit function did not work properly with alpha based edit masks and if the target was greater than 32 characters.

· Suprtool now treats KSAM64 files with labels as SD files, in the same manner as KSAMXL files are.

· A warning will print if a non-regular SD file is loaded into a Table with the data option. The data is not loaded into the table.

· An error will print if an extract command attempts to reference data when loaded from table that in turn was loaded when using a non-regular SD file, such as KSAM/XL, KSAM64 and CM KSAM.

Highlights in Suprtool 5.4

· Bradmark's DBGeneral can produce Jumbo datasets that are a single chunk, Suprtool did not handle these single chunk master jumbo datasets properly as the last block calculation was done only after opening the last chunk itself. We have adjusted the logic in making sure the calculation is done for this case earlier. Adager does not create these single chunk jumbo datasets. There is an un-documented $control directive in dbschema called $forcejumbo, which will produce one of these single chunk jumbos so we are supporting it in Suprtool 5.3.11.

· The Output command has been enhanced to accept the new verb "else", which when invoked it will write out the records that do not qualify and write them to an external file.

· Suprtool did not properly clear the data field information from a table at the end of a task.

· Suprtool did not properly zero out a packed field target when an table entry was not found when extracting data from a table.

Known Problems

Set Itemlock does not work in one particular case.

Compatibility

Suprtool/iX is compatible with MPE V, MPE XL, and MPE/iX, including MPE/iX 6.5, 7.0 and MPE/iX 7.5.

Suprtools default prefetch value has been changed from 2 to zero.

A warning will print if a non-regular SD file is loaded into a Table with the data option. The data is not loaded into the table.

An error will print if an extract command attempts to reference data when loaded from table that in turn was loaded when using a non-regular SD file, such as KSAM/XL, KSAM64 and CM KSAM.

CPU Serial Number and CPU Name (HPSUSAN & HPCPUNAME)

Suprtool and its associated products run only on CPUs whose serial numbers have been encoded ("showvar hpsusan" on MPE/iX). They also may be encoded with your HPCPUNAME values. If it fails to run and you get an "invalid HPCPUNAME" or "invalid HPSUSAN" error message, contact Robelle for assistance.

Documentation

The user manual contains the full description of all the Suprtool suite of products including Dbedit, Suprlink, STExport and Suprtool2, as well as usage tips and commands for each. The manuals are up-to-date with all the latest changes. To see only the changes in the latest version, see the "What's New" section of the manual, or see the change notice.

You can download our manuals and change notices in various formats and you can order printed (hardcopy) manuals from our web site at:

http://www.robelle.com/library/manuals/

Installation

Overview

We have two types of Installations, Tape and Download. We provide links to the Installation instructions on our web site for each type of Install.

Installation Instructions

If you received a production release tape from Robelle, then you can install using the instructions on this web page:

http://www.robelle.com/support/install/tape/stprod.html

If you downloaded the Suprtool production release from our web site then the instructions can be found here for the ftp download method:

http://www.robelle.com/downloads/install-stprod-ftp.html

and here for the WRQ download method:

http://www.robelle.com/downloads/install-stprod-wrq.html

Installation Assistance

If you have any questions about the upgrade process or run into any problems, please call us. Technical support is available on weekdays from 8 a.m. to 4 p.m. Pacific time at 800.453.8970 or you can e-mail your question to support@robelle.com.

Enhancements in Version 5.5

Introduction

Suprtool is constantly being updated with new features. The following section describes the new enhancements to Suprtool since Suprtool 5.4.

Set XLTRIM

Suprtool now has the command Set xltrim on, which tells Suprtool to close the output file in a manner in which it releases the disc space between EOF and the Flimit, but the Flimit remains the same. This trim will only occur of set squeeze is not set or if set squeeze is off.

Input Command

Suprtool now treats KSAM64 files the same as KSAMXL files when they have labels and are properly recognized as self-describing files.

Escape Command

STExports Escape command has been revised to be faster and a couple of corner cases.

Enhancements in Version 5.4

Introduction

Suprtool is constantly being updated with new features. The following section describes the new enhancements to Suprtool since Suprtool 5.3.

Get Command

Bradmark's Adager can produce Jumbo datasets that are a single chunk, Suprtool did not handle these single chunk master jumbo datasets properly as the last block calculation was done only after opening the last chunk itself. We have adjusted the logic in making sure the calculation is done for this case earlier. Adager does not create these single chunk jumbo datasets. There is an un-documented $control directive in dbschema called $forcejumbo, which will produce one of these single chunk jumbos so we are supporting it in Suprtool 5.3.11.

Output Command

The Output command has been enhanced to accept the new verb "else", which when invoked it will write out the records that do not qualify and write them to an external file.

Consider the following task:

base mydb

get customers

if custno >= "50A"

out mycusts,link,else

xeq

Suprtool will create two files one called mycusts and another called else which will be a temporary file. This works for flat files, Image (via get and chain) and KSAM files. The temporary ELSE file will NOT prompt if there is a duplicate. It will simply purge the file prior to creating the new temporary file. You can of course use file equations to re-direct the output to another named temporary file but the user is responsible for insuring that the file equated filename doesn't exist so that the write operation will work.

You cannot combine output ,else with the num or key options. In this case Suprtool will tell you it is ignoring the ,else operation. You cannot combine output,else with any of the dup or nodup options or the duplicate command. Suprtool will generate an error in this case.

Enhancements in Previous Versions

Introduction

Suprtool is constantly being updated with new features.

ZonedFix

STExport now has Set ZonedFix On, this setting can be used to zero out any zoned fields that were unable to be converted from zoned to byte and typically have a "?" in the result. This is often caused by hidden characters or bad data.

$stddate($days(a))

Suprtool now allows for the $days function to be nested in the $stddate function.

ext a=$stddate($days(a) + 1)

list

xeq

>IN TEST.GROUP.ACCOUNT (0) >OUT $NULL (0)

A = 20080319

TPI-keys

Suprtool now supports stand-alone Zoned-decimal TPI-keys, for Omnidex and Superdex. Previously Suprtool only supported byte type keys. Suprtool now supports stand-alone “Z” type keys, Suprtool's form command will show the keys that it can support via the chain command.

The length of a key is returned by dbinfo-833 and Suprtool will report in the form command the length of a stand-alone key. (SI-PRODUCT-NO is the path that is now supported) Superdex has a variable that impacts the length that is returned for a given key, and that is SICOGNOS. Suprtool will account for the length difference on the chain command but will show the unadjusted length. Normally Superdexs dbinfo-833 would show a length of 12 for a Zoned-decimal tpi-key with a length of 8, if SICOGNOS is set to 1, then Superdex will return 8.

form d-inventory

Database: STORE.SUPRTPIS.GREEN TPI: SUPERDEX (010566) 4.2.11.2

D-INVENTORY Detail Set# 4

Entry: Offset

BIN-NO J1 1

LAST-SHIP-DATE J2 3

ON-HAND-QTY J2 7

PRODUCT-NO Z8 11 (M-PRODUCT)

<<TPI>>

SUPPLIER-NO Z8 19 (!M-SUPPLIER)

UNIT-COST P8 27

ITEM-DESC1 X20 31 <<TPI>>

ITEM-DESC2 X20 51

ITEM-DESC3 X20 71

ITEM-DESC4 X20 91

Capacity: 464 (8) Entries: 13 Highwater: 13 Bytes: 110

Additional Third-Party Indexes:

SI-PRODUCT-NO Z8 B

SI-ITEM-DESC1 X20 B

SI-ITEM-DESC1234 X80 B

SHAD X10 B

VarsubDebug

Suprtool, STExport and Suprlink now have a setting called Set VarsubDebug on which will print out the line after the variable substitution has occurred. This setting only works if Set Varsub is on and Set VarsubDebug is on.

setvar outfile &

:"/GREEN/SUPRTEST/filename90123456789012345678901234567890123456789012345678901"

:run suprtool.pub.robelle

(Version 5.0.11 Internal) TUE, OCT 30, 2007, 2:58 PM Type H for he

>set varsub on

>set varsubdebug on

>in file1sd.suprtest

vd:in file1sd.suprtest

>output !outfile,link,temp

vd:output /GREEN/SUPRTEST/filename90123456789012345678901234567890123

vd:2345678901,link,temp

The output is formatted into 74 byte chunks and printed with a preceding “vd:” so the “substituted” line is clear.

If $lookup

Suprtool's IF command is now able to use the “data” loaded into a Table. The $lookup function will return the data value from the table to compare against another field or literal.

In file1sd

Table mytable,char-field,data,tabfile,data(id-field)

If $lookup(mytable,char-field,id-field) = int-field

So what Suprtool will do in this case is read a record, lookup the record in the table and retrieve the data item in the table. If Suprtool does NOT find an entry in the table, a zero will be returned if the data type is numeric and spaces will be returned if it is a byte type.

So using the case above, if no entry is found in the table, zero is returned, and if int-field is equal to zero, then the record will qualify.

If you don’t want to have any values returned from the table lookup, you just preface the if with a standard lookup.

>get ord-details

>table cust-table, cust-no, file, custlist,data(state-code)

>if $lookup(cust-table,cust-no) and &

$lookup(cust-table, cust-no, state-code) = state-code

>output orders

>xeq

When using $lookup to return data, the $lookup must always be on then left side of the expression. If not Suprtool will stop with an error:

>if id-field=$lookup(mytable,char-field,id-field)

Error: $lookup in this context (data comparison) must be on left side

Multiple literal comparison

Suprtool can now do multiple literal comparisons, previously Suprtool was only able to compare two sets of literals.

If “a” = “a” and “b” = “b”

If “a” <> “b” and “b” <> “c”

KSAM and If command

For the last two production versions Suprtool was slowed down for reading of NM KSAM files if an IF command was specified due to a bug in MPE. Suprtool now reads NM KSAM files in MR NOBUF mode again in all cases.

Bugs Fixed

Bugs Fixed In Suprtool 5.5

Ksam64 files. Ksam64 files were not assumed to be Self-describing like CM KSAM and KSAMXL files when it was the input file and had labels.

$edit function. The $edit function did not work well with alpha based edit masks and if the target was greater than 32 characters.

Table File Data Load. A warning will print if a non-regular SD file is loaded into a Table with the data option. The data is not loaded into the table.

Table File Data Lookup. An error will print if an extract command attempts to reference data when loaded from table that in turn was loaded when using a non-regular SD file, such as KSAM/XL, KSAM64 and CM KSAM.

BTrees and Chain. Due to an issue with Btrees, Suprtool would incorrectly select records when doing an update or delete, and if using chain with a btree index on a master dataset.

Bugs Fixed In Suprtool 5.4.01

Output, Else. Suprtool would not print a warning when output,else was specified during a sort operation.

GET Command. The Get command would get too many records if the dataset was a single chunk jumbo dataset. Only Dbgeneral and dbschemas $forcejumbo can make these single chunk datasets.

Table Command. Suprtool did not properly clear the data field information from a table at the end of a task.

Extract from Table. Suprtool did not properly zero out a packed field target when an table entry was not found when extracting data from a table and the Packed field was P12 or higher.