cobol compiler for suse

5 More Discussions You Might Find Interesting

1. Red Hat

Install cobol compiler

Hi I dont have a cobol compiler in my redhhat linux box, and so I want to install it. When i try the below command sudo apt-get install open-cobol it tells "apt-get : command not found". I tried to find apt-get under my root, could not find it anywhere. Should we install apt-get also?...

2. Shell Programming and Scripting

cobol help....compiler key and its usage....

i am having mfcobol old version... which was supplied by my friends....with a compiler key (h/w) having 24 pin male on one side and 24 pin female on the other side....with lable LOPOEK XXXXXXXXXX MICRO FOCUS........ AM USING NORMAL COMMANDS USING .CBL, .OBJ, .LIB FILES TO GET COBOL EXE FILE.......

3. 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. ...

4. Programming

How Can a Machine Reads a Compiler Since A Compiler is Written in Text! Not Binaries?

To make a programming language you need a compiler, so what was the first programming language and how was is created if you need the compiler first? The compiler itself is considered as a high language comparing to the machine! since the compiler is not created in 1's and 0's... Eventhough i...

5. 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

LEARN ABOUT SUSE

ifcfg-vlan

IFCFG-VLAN(5)						       Network configuration						     IFCFG-VLAN(5)

NAME

       ifcfg-vlan - virtual LAN interface configuration

SYNOPSIS

       /etc/sysconfig/network/ifcfg-vlan*

Virtual LANs (802.1q)
       To setup a vlan interface you need a configuration file that contains at least the mandatory

       ETHERDEVICE
	      variable with the real interface used for the virtual LAN.

       Further, it may contain the optional

       VLAN_ID
	      variable that specifies the VLAN ID.

       By default and when the VLAN_ID variable is not set, the number at the end of the interface name is the VLAN ID.

       Preferably the interface name and the configuration file follow the VLAN interface name scheme (type), that is either:
	      ifcfg-vlan<VLAN-ID> (e.g. ifcfg-vlan42)

	      or

	      ifcfg-name.<VLAN-ID> (e.g. ifcfg-eth0.42)

       The VLAN-ID can be also 0-padded (e.g. ifcfg-vlan0042 or ifcfg-eth0.0042).

       Also  in case of custom names, trailing digits are interpreted as VLAN-ID by default (e.g. ifcfg-dmz42). When VLAN_ID is set in the config,
       the interface name have any name (e.g. ifcfg-foobar).

       Note: The drawback of custom interface names and VLAN_ID usage is, that a rename of the interface is required and  that	they  violate  the
       name scheme.

       The  real  interface will be set UP automatically and doesn't need a config file in case of a physical interface. But without a config file
       YaST will consider this interface as unused, if will not follow hotplug	events	and  you're  unable  to  apply	any  settings,	e.g.  ETH-
       TOOL_OPTIONS. To avoid that, provide an config file with at least STARTMODE='auto'.

       The  rest  of  the VLAN interface IP and routes configuration do not differ from ordinary interfaces. See also man ifcfg and man routes for
       details.

EXAMPLES

       Sets up vlan3 vlan interface on top of eth0:

	      ifcfg-vlan3
		 STARTMODE='auto'
		 ETHERDEVICE='eth0'
		 IPADDR='192.168.3.27/24'

       Sets up eth0.3 vlan interface on top of eth0:

	      ifcfg-eth0.3
		 STARTMODE='auto'
		 ETHERDEVICE='eth0'
		 IPADDR='192.168.3.27/24'

       Sets up lan1 vlan interface with ID 42 on top of eth0:

	      ifcfg-lan1
		 STARTMODE='auto'
		 ETHERDEVICE='eth0'
		 VLAN_ID='42'
		 IPADDR='192.168.3.27/24'

BUGS

       Please report bugs at <http://www.suse.de/feedback>

AUTHOR

       Christian Zoz <zoz@suse.de>
       Michal Svec <msvec@suse.cz>
       Bjoern Jacke
       Mads Martin Joergensen <mmj@suse.de>
       Michal Ludvig <mludvig@suse.cz>
       Marius Tomaschewski <mt@suse.de>

SEE ALSO

       routes(5), ifcfg(5), ifup(8).

sysconfig							    August 2004 						     IFCFG-VLAN(5)

Programming