Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
HP.com home

LFDS Detection Tool Information

» 

Business systems evolution

Site information

» Features archive
» Newsletters

HP e3000 program

» Home
» Transition training
» MPE/iX education
» Case Studies
» How to buy
» Technical resources
» Information library
» European information

Learn more about

» Linux® on HP Integrity servers
» Microsoft® Windows®
Content starts here

What is LFDS Detection Tool?

The LFDS Detection Tool was written to help facilitate locating any LFDS capable database on your system. It is run as part of the installation process for the TurboIMAGE C.10.10 "LFDS Disable" patch TIXMXW7 (or superseding patch) and may also be run by the system manager of your systems to periodically check for the existence of any LFDS capable databases.

The program is called LFDSDET and will reside in PUB.SYS after installation of TIXMXW7 (or superseding patch).

How Does The LFDS Detection Tool Work?

The LFDS Detection Tool operates in two modes:

  • Installation mode, used when the program is run as a part of a patch installation or when run manually after a patch installation because a of problems that may have occurred during installation and
  • Normal mode, used day-to-day to check for the existence of LFDS capable databases.

When LFDSDET is run in "installation mode" it will scan ALL of the databases on your system. In "normal mode" you must supply a file set to it via the "INFO" string of the run command. This file set is identical to that used for the MPE "LISTFILE" command. For example:

:RUN LFDSDET.PUB.SYS;INFO="@.DB.AP"

Each database LFDSDET is to scan is opened for shared read-only access. Only the root file is checked to find out the database version and to examine a field in the root file called the "root features bits". These indicate whether the database uses Master Dataset Expansion (MDX), Detail Dataset Expansion (DDX) and whether the LFDS feature is enabled.

Note: LFDSDET does not read any of the datasets in your database and makes no changes to your database. The first record of the root file is the only thing examined by the program.

Installation Mode

As mentioned earlier the "installation mode" feature of LFDSDET is used when the program is run as part of the patch installation process. However it may also need to be used after installation of the TIXMXW7 (or superseding) patch if problems occurred during initial installation. Running LFDSDET in "installation mode" is accomplished by specifying "1234" via the "PARM" option of the run command. For example:

:RUN LFDSDET.PUB.SYS;PARM=1234

Note that no file set is necessary when the LFDS detection tool is run in installation mode as all databases on your system must be checked.

Note: LFDSDET must be run by someone logged on as MANAGER.SYS when run in installation mode. When run in normal mode the person running LFDSDET must be logged on only as a user that has system manager (SM) capability.

LFDSDET:Large File Dataset Detection Tool C.01.01 TUE, JUN 13, 2006,  7:49 AM
(C) Copyright Hewlett-Packard Development Co.,LP 2006

TurboImage Version: C.10.05

Database: DMON.DESKMON.HPOFFICE      VERSION: C.02  LFDS: N MDX: N DDX: N
Database: TELBAS.HPTELEX.HPOFFICE    VERSION: C.02  LFDS: N MDX: N DDX: N
Database: GLOBAL.MAILDB.HPOFFICE     VERSION: C.02  LFDS: N MDX: N DDX: N
Database: LOCAL.MAILDB.HPOFFICE      VERSION: C.02  LFDS: N MDX: N DDX: N
Database: TOYDB.PUB.ITF3000          VERSION: C.02  LFDS: N MDX: N DDX: N
Database: BIGDB.PERFTEST.LFDS        VERSION: C.07  LFDS: Y MDX: Y DDX: Y <C10
Database: OPSDB.PRED.SYS             VERSION: C.04  LFDS: N MDX: Y DDX: Y
Database: PROCDB.PUB.SYS             VERSION: C.02  LFDS: N MDX: N DDX: N
Database: CONFIG.COMMON.SYSMGR       VERSION: C.02  LFDS: N MDX: N DDX: N      
Database: EML001.COMMON.SYSMGR       VERSION: C.02  LFDS: N MDX: N DDX: N
 
Totals:
Databases selected               : 10
Databases checked                : 10
Databases not checked            : 0
Total with LFDS but no MDX or DDX: 1
Total with LFDS using MDX or DDX : 1
Total all LFDS enabled databases : 1

In this example 10 databases were found on the system and checked, 1 of which is LFDS capable and uses both Master Dataset Expansion (MDX) and Detail Dataset Expansion (DDX). This means that the dataset may not now be larger than 4 gigabytes but it could eventually be larger than that. Also shown is a tag "<C10" indicating that the LFDS format is that delivered with the C.10.xx version of TurboIMAGE.

Additional information displayed includes the overall TurboIMAGE version, C.10.05 in this example as well as the internal database versions which indicates which level of features were supported at the time the database was created.

If any of the databases could not be accessed due to mode or other conflicts that would be displayed in place of the version and feature information, for example:

:lfdsdet '@.pub.sys'

LFDSDET:Large File Dataset Detection Tool C.01.01 TUE, JUN 13, 2006,  8:13 AM
(C) Copyright Hewlett-Packard Development Co.,LP 2006
 
TurboImage Version: C.10.05 
 
Database: PROCDB.PUB.SYS             Database opened in an incompatible mode.  
 
Totals: 
Databases selected               : 1
Databases checked                : 0
Databases not checked            : 1
Total with LFDS but no MDX or DDX: 0
Total with LFDS using MDX or DDX : 0
Total all LFDS enabled databases : 0

Here only one database was found in the file set @.pub.sys and it was opened in an incompatible mode (mode 3 or mode 7). If an unexpected file system error occurs trying to open a database the information about the failure would be displayed in a similar way, showing the error message or error that occurred.

Recommended Actions

The LFDS detection tool will make a brief recommendation upon detecting LFDS capable databases on your system. This is true for both installation mode and normal mode. The recommendation will depend on the attributes of the LFDS capable database found as compared to the version of TurboIMAGE installed on your system. For the most up-to-date, comprehensive information please see What To Do If LFDS Databases Exist On Your System.

When run in installation mode the LFDS detection tool will also ensure the system manager knows that there were LFDS capable databases on your system by requiring an acknowledgement. When the tool is run in batch mode this will be sent to the system console otherwise it will be issued to the STDLIST/STDIN devices. For example:

7:22/#J6/60/+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
7:22/#J6/60/+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
7:22/#J6/60/+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
7:22/#J6/60/
7:22/#J6/60/The following databases are enabled for LFDS:
7:22/#J6/60/
7:22/#J6/60/BIGDB.PERFTEST.LFDS
7:22/#J6/60/
7:22/#J6/60/Actions must be taken to ensure continued data integrity.
7:22/#J6/60/Please refer to the STDLIST of this job for remedies.
7:22/#J6/60/
7:22/#J6/60/+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
7:22/#J6/60/+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
7:22/#J6/60/+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
7:22/#J6/60/
7:22/#J6/60/Please respond by replying with the word AGREE.
?7:22/#J6/60/(LFDSDET) Please supply your response. (MAX CHARS.=31)?

You must respond to the prompt with the word "AGREE" (case insensitive). Failing to do so will cause the message to be issued again. This ensures that the system manager is alerted to the presence of LFDS capable databases on your system. Please note that this additional alert is only issued when the LFDS detection tool is run in "installation mode".

Disabling Writes To LFDS Capable Databases

When LFDSDET is run in installation mode it will create a file called "HPNOLFDS.PUB.SYS" if it finds that there are NO LFDS capable databases on your system. The presence of the properly qualified HPNOLFDS file signals to the C.10.10 TurboIMAGE code installed with the TIXMXW7 (or superseding) patch that writes should be disabled to any LFDS capable database. This prevents difficulties that might occur if an LFDS capable database were later restored to your system.

If any LFDS capable databases ARE found on your system this HPNOLFDS file is NOT created. If a properly qualified HPNOLFDS already exists from a prior run that file is purged.

If NO LFDS capable databases are found then HPNOLFDS is created or re-created (purged and rebuilt) if it already exists from a prior run.

When the LFDS detection tool is run in normal mode and a properly qualified HPNOLFDS is found in PUB.SYS the file is used as a log file and the date, time, user who ran LFDSDET and the job or session they were logged on with is written into the file. The HPNOLFDS file can be printed using the MPE "PRINT" command.

Note: If LFDSDET is unable to check all the databases on your system because of difficulties possibly caused by any database opened exclusively or due to any other access problem it WILL NOT create the HPNOLFDS file even if it has not yet found any LFDS capable database. You should only install the TIXMXW7 (or superseding) patch or run LFDSDET in installation mode when databases on your system are not being accessed to ensure a complete and accurate scan of your system.

Delivery of The LFDS Detection Tool

The LFDS Detection Tool is delivered with the TIXMXW7 TurboIMAGE C.10.10 (or superseding) patch.

LFDS Detection Tool Frequently Asked Questions

Q: Can anyone run the LFDS detection tool?

A: When run in "normal mode" only people logged on as a user with system manager (SM) capability may run the LFDS detection tool. When run in "install mode" the person running the tool must be logged on as the user "MANAGER.SYS".

Q: Can I run the LFDS detection tool any time I wish?

A: If data is frequently restored to your system from other systems it would be wise to periodically run the detection tool to see whether any LFDS capable C.10.xx version databases have been restored to your system. You should try to run the LFDS detection tool when databases on your system are not being accessed or are opened in a sharable mode (modes 1,2,4,5,6 or 8) so that the LFDS detection tool can also open them for shared, read access.

Q: If I have systems on different MPE releases, which systems must I be sure to run the LFDS detection tool on?

A: You should run the LFDS detection tool on any system running TurboIMAGE versions C.10.03 through C.10.09 or on any system that had been running one of these versions. When it doubt, run the tool.

Q: Should I run it in "install mode" or in "normal mode"?

A: You should always run the LFDS detection tool in "normal mode" unless you have been instructed to re-run it in "install mode" to correct a problem that may have occurred during patch installation.

Q: What happens if the LFDS detection tool fails to run correctly during installation of TIXMXW7 (or superseding patch)?

A: The patch will still install correctly. However, you will need to address the reason why the tool failed to run and re-run the tool using "install mode" at your earliest convenience. The most common cause for the tool failing to run to completion would be if it could not access ALL the databases on your system. This could happen if some were open MODE 3 or MODE 7, or if they were opened exclusively by a database management utility or other system operation.

Q: When does the LFDS detection tool create the "HPNOLFDS" file?

A: The LFDS detection tool will create the HPNOLFDS file in the PUB group of the SYS account when the tool is run using "install mode" and when it has found NO LFDS capable C.10.xx databases on your system.

Q: What happens if the HPNOLFDS file is purged?

A: The file is protected so it should not be possible to accidentally purge it. If it is purged then the C.10.10 TurboIMAGE code will assume there are LFDS capable C.10.xx databases on the system and permit writes to them. If there are no such databases on your system then no harm will be done. However you would need to re-run the LFDS detection tool using "install mode" at your earliest convenience to recreate the HPNOLFDS file.

Q: If the HPNOLFDS file is purged can't I just build it?

A: No, the file has unique attributes and content that identify it as coming from the LFDS detection tool. Simply building a file with that name will not prevent TurboIMAGE from allowing writes to LFDS capable C.10.xx databases if such databases exist on your system.

Q: What would happen if I already had a file called HPNOLFDS on my system from another source?

A: The chances of that are fairly small but not zero. If the LFDS detection tool discovers a file called HPNOLFDS on your system that was NOT created by a prior run of the tool it will do nothing if it had already discovered LFDS capable C.10.xx databases on your system. This is because this foreign file will not disable writes from TurboIMAGE. However, if it has found NO LFDS capable C.10.xx databases on your system it will issue a lengthy message to STDLIST and to the system console, if run in batch mode informing you of this. You will need to determine how the file came to be there and move it if possible. Once this foreign file is moved or purged you will need to run the LFDS detection tool in "install mode" again to ensure that the HPNOLFDS file recognized by TurboIMAGE is created.

Q: Can I run the LFDS detection tool on any release of MPE/iX?

A: Yes, the tool does not change any of your databases. The tool has been tested on MPE/iX 6.5, 7.0 and 7.5. No release prior to MPE/iX 6.5 supported LFDS so there is no reason to run it on those. 

Q: I decided to download and install the version of DBSCHEMA that prevents creating an LFDS database, should I run the LFDS detection tool and if so, in what mode?

A: This version of DBSCHEMA will prevent you from accidentally creating an LFDS capable database on C.10.xx but to be sure you have no existing LFDS capable databases you should run the LFDS detection tool in "normal mode". Since you have not yet installed the TIXMXW7 (or superseding) patch you do not yet have the code that can prevent writes to an LFDS capable C.10.xx database if the HPNOLFDS file is present so there is no value in running the LFDS detection tool in "install mode".

Q: What if I do run it in "install mode" with just the DBSCHEMA replacement?

A: No harm, the HPNOLFDS file will be built in PUB.SYS and will not cause any change in the behavior of TurboIMAGE. When you do finally install the TIXMXW7 (or superseding) patch the LFDS detection tool will see that the existing copy of HPNOLFDS was created by the tool so it will purge that old copy and create a new one.

What to do if the LFDS Detection Tool finds an LFDS database?

The following are the steps needed to migrate from LFDS on C.10.xx. There are a few exceptions, which apply on 7.5 only. These recommendations describe using HP supplied utilities.

If you need set(s) >4 GB and you can manage without DDX/MDX on any set >4GB then you should convert to using Jumbo instead of LFDS:

  1. Back up your database
  2. DBUNLOAD database
  3. Install C.10.10 LFDS disable patch TIXMXW7 (if not already installed)
  4. Alter the schema file to
    • remove any $CONTROL LFDS statement
    • include $CONTROL JUMBO before the specification of any sets >4GB.
    • remove DDX/MDX specification for any set >4GB
  5. Purge the database with DBUTIL
  6. Recreate the database from the schema file using DBSCHEMA, DBUTIL
  7. Reload the data with DBLOAD.
  8. Back up the new copy of your database.

If there is really no need for any set to be >4GB then you may recreate the database without Jumbo or LFDS:

  1. Back up your database
  2. DBUNLOAD database
  3. Install the C.10.10 LFDS disable patch TIXMXW7 (if not already installed)
  4. Alter the schema file
    • change maximum capacities so that no set is >4GB
    • remove any $CONTROL LFDS statement
  5. Purge the database with DBUTIL
  6. Recreate the database from the schema file using DBSCHEMA, DBUTIL
  7. Reload the data with DBLOAD.
  8. Back up the new copy of your database.

Exceptions

LFDS created on C.10.03 but Current Version not C.10.03

C.10.03 was the version shipped on base 7.5. It was never available on any other release.

If you have a LFDS created on C.10.03 and you are currently running C.10.04 and there is data beyond 4GB - DBUnload may not work. This is because the LFDS structure changed, and a C.10.04 or later DBUnload may not be able to read beyond 4GB. If this issue was experienced with LFDS on C.10.03, rebuilding on a later version should have been recommended. So this situation should indeed be exceptional.

There is no way to distinguish internally, via the root file, between an LFDS database created on C.10.03 and one created on a later C.10.xx version. If the creation date of your LFDS database is earlier than the date any Image patch was installed on your 7.5 then you could be in this situation. The patch install date should be available from hpswinfo.pub.sys. If you are in this situation then the database would need to be unloaded on a C.10.03 system, before following step 2 onward in the above instructions.


** About PDF files: The PDF files on this Web site can be read online or printed using Adobe® Acrobat® Reader. If you do not have this software installed on your system, you may download it from the Adobe Web site.
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 2009 Hewlett-Packard Development Company, L.P.