Sponsored Content
Full Discussion: OS upgrade
Operating Systems AIX OS upgrade Post 82204 by GEIER on Monday 29th of August 2005 04:20:39 PM
Old 08-29-2005
Thanks for your help chap.


Kind regards!!!
 

4 More Discussions You Might Find Interesting

1. Solaris

help for Upgrade

hi administrator i need help to find solution for this . i have sun fire v880 server with configuration metioned below sun fire v880 2*750 MHz UltraSPARC 111 with 4 GB Memory ( 256*16 ) 36*6 GB hard disks( Internal) with other configuration and now i need to upgrade this server.... (3 Replies)
Discussion started by: dhasanka
3 Replies

2. AIX

upgrade 5.2 to 5.3

Hello ,, I have OS AIX 5.2 ML 5200-05 Model : 9113-550 we want upgrade 5.2 to 5.3 how I can upgrade 5.2 to 5.3? (3 Replies)
Discussion started by: AIX122
3 Replies

3. Red Hat

Upgrade

Dear all, Requirement: Upgrade RHEL 3 to RHEL 5. Question: How to plan the upgrade? Present state: Know that there is no direct upgrade path visible. And RH does not support direct upgrade. H/W: HP Proliant DL 380 G4 TIA (1 Reply)
Discussion started by: earlysame55
1 Replies

4. Red Hat

Upgrade from OL 6.3 to 6.5

Hello, For upgrading from OL 6.3 to 6.5 is this possible to upgrade without rebuild? What should be the generic steps in migration to OL 6.5. IS this like building up from scratch ? Best regards, Vishal (4 Replies)
Discussion started by: admin_db
4 Replies
lname_component(3erl)					     Erlang Module Definition					     lname_component(3erl)

NAME
lname_component - Interface that supports the name pseudo-objects. DESCRIPTION
This interface is a part of the name library, which is used to hide the representation of names. In Orbers Erlang mapping the pseudo-object names and the real IDL names have the same representation but it is desirable that the clients uses the names library so they will not be dependent of the representation. The lname_component interface supports handling of name components e.g. set and get of the struct members. Note that the lname_component interface in orber does not contain a destroy function because the NameComponents are represented as Erlang records and therefor will be removed by the garbage collector when not in use. The type NameComponent used below is defined as: -record('CosNaming_NameComponent', {id, kind=""}). id and kind are strings. The record is defined in the file CosNaming.hrl and it is included with: -include_lib("orber/COSS/CosNaming/CosNaming.hrl"). EXPORTS
create() -> Return Types Return = NameComponent This function returns a new name component. get_id(NameComponent) -> Return Types Return = string() This function returns the id string of a name component. set_id(NameComponent, Id) -> Return Types Id = string() Return = NameComponent This function sets the id string of a name component and returns the component. get_kind(NameComponent) -> Return Types Return = string() This function returns the id string of a name component. set_kind(NameComponent, Kind) -> Return Types Kind = string() Return = NameComponent This function sets the kind string of a name component and returns the component. Ericsson AB orber 3.6.20 lname_component(3erl)
All times are GMT -4. The time now is 02:13 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy