VERSYS Legacy System


 
Thread Tools Search this Thread
Top Forums Programming VERSYS Legacy System
# 1  
Old 04-28-2010
VERSYS Legacy System

I need help locating the tables that hold the demograhic data in this system on an AIX box. Does anyone know the path?
Login or Register to Ask a Question

Previous Thread | Next Thread

6 More Discussions You Might Find Interesting

1. Solaris

Determine if you are in a Legacy Zone?

Hi Folks, Just a quick question here, about Legacy Zones. Well more about how to determine if you are actually in one, on logging into a legacy zone - is there a quick way of checking that? Regards Gull04 (7 Replies)
Discussion started by: gull04
7 Replies

2. SCO

Need Help Installing Legacy System on Newer Hardware

We have a legacy software application that runs on SCO OpenServer 5.0.6, and the current server (built around 2003-04) is still running. I have been attempting to upgrade the hardware, to hopefully increase the time that we will have access to the data in this system, but am running into an... (13 Replies)
Discussion started by: spock9458
13 Replies

3. Solaris

NFS server on Legacy Container?

Hi All, I have a problem as follows. Historically, there was an Ultra10 workstation running Solaris 8 using automount to access NFS volumes on a Solaris 8 server. The Ultra 10 was retired and the Solaris 8 server has been migrated to a Legacy Container (Solaris 8 Branded, whole root,... (9 Replies)
Discussion started by: hicksd8
9 Replies

4. What is on Your Mind?

Tron Legacy

Watched it. Major disappointment. (10 Replies)
Discussion started by: ni2
10 Replies

5. Solaris

How to set up legacy services right on Solaris 10

I want to add auto startup and shutdown script to Solaris 10's legacy services as they run in Solaris 9 or in Linux. To make this work, I created the crontrol script in /etc/init.d and then link it to /etc/rc0.d and /etc/rc2.d directories. rc0.d is for shutdown and rc2.d is for srat. After I... (15 Replies)
Discussion started by: duke0001
15 Replies

6. Programming

CMI Legacy

Is there anyone who still uses CMI to connect to the legacy system , my c applications do uses the binaries and libraries for using the CMI functionality but i do not have access to the original source code , and since this is a very old stuff , i just could not get any source to get to knwo the... (0 Replies)
Discussion started by: dino_leix
0 Replies
Login or Register to Ask a Question
idisk(1M)																 idisk(1M)

NAME
idisk - create partitions for disks on an Integrity system SYNOPSIS
partition_description_file}] device DESCRIPTION
creates operating system partitions for disks on an Integrity system. It reads in the partition information from a data file that may be specified in the command string or redirected from stdin. By default, operates in read-only mode and displays the partition information that is currently on the disk. To write new partition infor- mation on the disk the user must specify the option. Options recognizes the following options: Print the primary EFI partition header and partition tables. Print the alternate EFI partition header and partition tables. Print the legacy partition table that resides in the master boot record. writes partition information for the first four partition in the partition table in used by legacy DOS and Win- dows. This information is used as a backup in the event all the EFI information is corrupted. Print the first usable and last usable block numbers that are available to create partitions. First usable is the first block a partition can start on. Last usable is the last block that can be contained in a partition. These numbers are relative to the whole disk and do not take into account any partitions that may exist. They represent the total disk space that can be partitioned. Use the option to only print the values without headings. Work silently. No user prompts or warnings. For use in shell scripts. Validate EFI partition information. Does the same checks the driver does verifying that both the primary and alternate EFI partition headers and tables are correct. Returns two if either is bad and zero if both are correct. Restore the EFI partition headers and tables. This option checks both the primary header and tables and the alternate header and tables. If one is found bad it is restored from the other good ver- sion. One of either the primary or alternate header and tables must be good for this option to succeed. The option must be specified for information to be written to the disk. Remove all EFI partition headers and tables from the disk. This option also destroys the information contained in the MBR (master boot record). The option must be specified for information to be written to the disk. The partition_description_file contains the number of partitions to be created and the type and requested size of each partition. The filename may be specified here or redirected from stdin when the dash is used. Enable write mode. By default operates in read-only mode. To create and write partition information to the disk you must specify the option. Partition Description File The first entry in the partition description file is the number of partitions to create. The maximum number of partitions allowed is 12. This is followed by a line containing the type and size for each of the partitions. Recognized partition types are: and At least one EFI partition is required to create a valid partition table. Size may be specified in megabytes or as a percentage of the whole disk. Internally, creates the partitions whose size is specified in MB first then creates those whose size was specified as a percentage. Those partitions specified as a percent are assigned space from what is available after the MB partitions are created. If the size of a parti- tion is specified as 100% then all space remaining is assigned to that partition. An example partition description file is shown below: The first entry specifies the number of partitions to create. The second specifies an EFI partition of 100 megabytes. The last entry specifies a HPUX partition consisting of all the remaining space on the disk after the EFI partition has been created. When creating partitions, the device file name must be that of the whole disk. Legacy device files must not have any partition number bits set in the minor number. For legacy disk devices, the last eight bits of the minor number represent the option bits. For Integrity system disks, the last four option bits are used to indicate the partition number. Since there are only four bits for parti- tion number, only one to fifteen partitions are supported. For example, a device node with a minor number of 0x008001 would indicate a disk at target eight, partition number one. A minor number of 0x00500F would indicate a disk at target 5 partition fifteen. A minor num- ber with no partition bits set would indicate the whole disk (for example, 0x008000 would be the same disk as above but represent the whole disk and not a partition). Persistent device special files do not use or contain minor number information. A detailed description on persistent device special files can be found in intro(7). Note: For partitions created by device special files must be created for each legacy hardware path to the disk and for the LUN hardware path using or (see intro(7) for details on legacy and agile modes). If legacy mode is disabled (see the descrip- tion of the option in rmsf(1M)), device special files must only be created for the LUN hardware path. Note has been ported to Windows NT 4.0 and 2000. RETURN VALUE
Exit values are: Successful completion. Error condition occurred. EXAMPLES
Create the partitions specified in the above description file, printing only the primary partition information: Create the partitions specified in the above description file, printing only the primary partition information using a persistent device special file (see intro(7)): Create the partitions specified in the above description file, printing all available information (default), redirecting input from stdin: Only read the disk, printing all tables (default) on the disk: Get the first and last usable block for partitioning on the disk: Destroy all partition information on the disk: Restore partition information from either a good primary or alternate header or table to the header or table that is bad: AUTHOR
was developed by HP. SEE ALSO
insf(1M), mksf(1M), efi(4), intro(7). Integrity Systems Only idisk(1M)