Sponsored Content
Operating Systems SCO Virtualize SCO 5.0.6 with Microfocus COBOL - Help needed Post 302759469 by sopela123 on Tuesday 22nd of January 2013 10:50:00 AM
Old 01-22-2013
Hi all,

We are running OCDS 4.1.40
I have reinstalled the micro focus license administration services, we do have a valid license (running in the machine that we want to virtualize and retire) but I don't seem to be able to export it.

Cheers
 

10 More Discussions You Might Find Interesting

1. Programming

cobol crn programme run on express cobol as .gnt

can i run .crn programme in express cobol which support to .gnt programme .... Plz tell me solution (2 Replies)
Discussion started by: bibi
2 Replies

2. Shell Programming and Scripting

Calling script from RM cobol and returning value to cobol

Is there a way you can return a value from a script that is called from a rm cobol program... 01 WS-COMD-LINE-PGM X(39) value sh ./getUserId.sh 12345" 01 WS-RETURN-SYS-CODE PIC 9(8). CALL "SYSTEM" USING WS-COMD-LINE-PGM GIVING WS-RETURN-SYS-CODE. ... (1 Reply)
Discussion started by: pavanmp
1 Replies

3. UNIX for Dummies Questions & Answers

UNIX Scripts "Load Error" with MicroFocus COBOL subprograms

When running our UNIX job scripts we randomly get the following 198 error below. When we restart the job it works fine. I haven't been able to recreate the problem in test, so I'm wondering if it has something to do with Cron or possibly a memory error or memory leak. I don't see anything... (5 Replies)
Discussion started by: rthiele
5 Replies

4. SCO

Virtualize physical SCO 5.0.6

hi Howto virtualize physical SCO 5.0.6 on ESX4? (22 Replies)
Discussion started by: ccc
22 Replies

5. SCO

SCO 5.0.6 Media needed

Hi, can anyone provide me the sources for sco 5.0.6 as iso? Thanks! (26 Replies)
Discussion started by: VoidCeroOne
26 Replies

6. SCO

Sco 5.0.6 Install ISO needed

Trying to restore a 5.0.6 server to a new server but the owner doesnt have their install media. Saw that many people have this. Please let me know of anyone that has a download link. Much appreciation! (1 Reply)
Discussion started by: gavinseabrook
1 Replies

7. SCO

Sco 5.0.6 installer needed

Hi I m sorry but to post this again. Does anyone have installer of sco 5.0.6 and instruction to reinstall the current system? This is urgent so Any help is appreciated. Thousand thanks (25 Replies)
Discussion started by: OrangeKenny
25 Replies

8. UNIX and Linux Applications

Ms COBOL 2.2 for SCO UNIX

HI ALL, I'm searching Ms Cobol 2.2 for Sco Unix if anyone has it please kind enough to support me... Thanks in advance Rukshan:) (2 Replies)
Discussion started by: rukshan4u2c
2 Replies

9. SCO

Sco media needed for openserver 5.0.6

Hello, i need if possible media for sco openserver 5.0.6 and also want to know if is possible to upgrade from 5.0.2 to 5.0.6. Best regards, Paolo (1 Reply)
Discussion started by: elnino981
1 Replies

10. SCO

SCO OpenServer 5.0.6 media needed

My media disk is unusable. Can someone provide me an ISO for Openserver 5.0.6? Thank you. Brantley Allen (2 Replies)
Discussion started by: brantleyallen
2 Replies
uname(1)							   User Commands							  uname(1)

NAME
uname - print name of current system SYNOPSIS
uname [-aimnprsvX] uname [-S system_name] DESCRIPTION
The uname utility prints information about the current system on the standard output. When options are specified, symbols representing one or more system characteristics will be written to the standard output. If no options are specified, uname prints the current operating sys- tem's name. The options print selected information returned by uname(2), sysinfo(2), or both. OPTIONS
The following options are supported: -a Prints basic information currently available from the system. -i Prints the name of the platform. -m Prints the machine hardware name (class). Use of this option is discouraged. Use uname -p instead. See NOTES section below. -n Prints the nodename (the nodename is the name by which the system is known to a communications network). -p Prints the current host's ISA or processor type. -r Prints the operating system release level. -s Prints the name of the operating system. This is the default. -S system_name The nodename may be changed by specifying a system name argument. The system name argument is restricted to SYS_NMLN char- acters. SYS_NMLN is an implementation specific value defined in <sys/utsname.h>. Only the super-user is allowed this capa- bility. This change does not persist across reboots of the system. Use sys-unconfig(1M) to change a host's name perma- nently. -v Prints the operating system version. -X Prints expanded system information, one information element per line, as expected by SCO UNIX. The displayed information includes: o system name, node, release, version, machine, and number of CPUs. o BusType, Serial, and Users (set to "unknown" in Solaris) o OEM# and Origin# (set to 0 and 1, respectively) EXAMPLES
Example 1: Printing the OS name and release level The following command: example% uname -sr prints the operating system name and release level, separated by one <SPACE> character. ENVIRONMENT VARIABLES
See environ(5) for descriptions of the following environment variables that affect the execution of uname: LANG, LC_ALL, LC_CTYPE, LC_MES- SAGES, and NLSPATH. SYSV3 This variable is used to override the default behavior of uname. This is necessary to make it possible for some INTERACTIVE UNIX Systems and SCO UNIX programs and scripts to work properly. Many scripts use uname to determine the SYSV3 type or the version of the OS to ensure software is compatible with that OS. Setting SYSV3 to an empty string will make uname print the following default values: nodename nodename 3.2 2 i386 The individual elements that uname displays can also be modified by setting SYSV3 in the following format: os,sysname,node,rel,ver,mach os Operating system (IUS or SCO). sysname System name. node Nodename as displayed by the -n option. rel Release level as displayed by the -r option. ver Version number as displayed by the -v option. mach Machine name as displayed by -m option. Do not put spaces between the elements. If an element is omitted, the current system value will be used. EXIT STATUS
The following exit values are returned: 0 Successful completion. >0 An error occurred. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ |Interface Stability |Standard | +-----------------------------+-----------------------------+ SEE ALSO
arch(1), isalist(1), sys-unconfig(1M), sysinfo(2), uname(2), nodename(4), attributes(5), environ(5), standards(5) NOTES
Independent software vendors (ISVs) and others who need to determine detailed characteristics of the platform on which their software is either being installed or executed should use the uname command. To determine the operating system name and release level, use uname -sr. To determine only the operating system release level, use uname -r. Notice that operating system release levels are not guaranteed to be in x.y format (such as 5.3, 5.4, 5.5, and so forth); future releases could be in the x.y.z format (such as 5.3.1, 5.3.2, 5.4.1, and so forth). In SunOS 4.x releases, the arch(1) command was often used to obtain information similar to that obtained by using the uname command. The arch(1) command output "sun4" was often incorrectly interpreted to signify a SunOS SPARC system. If hardware platform information is desired, use uname -sp. The arch -k and uname -m commands return equivalent values; however, the use of either of these commands by third party programs is dis- couraged, as is the use of the arch command in general. To determine the machine's Instruction Set Architecture (ISA or processor type), use uname with the -p option. SunOS 5.10 17 Sep 2003 uname(1)
All times are GMT -4. The time now is 01:40 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy