DCE RPC ON GCOS 7 - Bull On-line Support...

DCE RPC ONGCOS 7

Software Release Bulletin DPS

7000/XTA

NO

VASC

ALE

7000

Distributed Computing

REFERENCE47 A2 65CF 00

DPS7000/XTANOVASCALE 7000

DCE RPC ON GCOS 7Software Release Bulletin

Distributed Computing

April 1994

BULL CEDOC

357 AVENUE PATTON

B.P.20845

49008 ANGERS CEDEX 01

FRANCE

REFERENCE47 A2 65CF 00

The following copyright notice protects this book under Copyright laws which prohibit such actions as, but notlimited to, copying, distributing, modifying, and making derivative works.

Copyright Bull SAS 1994

Printed in France

Suggestions and criticisms concerning the form, content, and presentation of thisbook are invited. A form is provided at the end of this book for this purpose.

To order additional copies of this book or other Bull Technical Publications, youare invited to use the Ordering Form also provided at the end of this book.

Trademarks and Acknowledgements

We acknowledge the right of proprietors of trademarks mentioned in this book.

Intel® and Itanium® are registered trademarks of Intel Corporation.

Windows® and Microsoft® software are registered trademarks of Microsoft Corporation.

UNIX® is a registered trademark in the United States of America and other countries licensed exclusively throughthe Open Group.

Linux® is a registered trademark of Linus Torvalds.

The information in this document is subject to change without notice. Bull will not be liable for errors containedherein, or for incidental or consequential damages in connection with the use of this material.

40 A2 65CF Rev00 iii

Preface

DCE RPC on GCOS7 (DCE Remote Procedure Call for GCOS7) is one component ofBull's GCOS integration into OSF's DCE offer which integrates GCOS systems into theUNIX/DCE environment. This S.R.B. describes how to install DCE RPC on GCOS 7.

Bull Hardware Platform

This document may have generic references to a DPS7000 hardware platform. If so, suchreferences are applicable to all models of the following Bull system computers :

• DPS7000/200 and 300 series

• DPS7000/400 Series

• DPS7000/500 and 700 Series

• DPS7000/AX series,

Associated reading

This manual has been written for GCOS7 system administrators who will be installingDCE RPC on GCOS7. It should be read in conjunction with the following books:

• DCE RPC on GCOS7 Administration Guide,

• DCE RPC Ally Administrative Supplement.

For an explanation of terms and abbreviations used in this document, refer to theGlossary in GCOS DCE Overview.

DCE RPC on GCOS7 S.R.B.

iv 40 A2 65CF Rev00

Typographic conventions

This manual uses the following typographic conventions. They are based on those usedin the OSF DCE documentation:

Bold Filenames , command names etc. which you must type inexactly as indicated.

Italic Variable values which you must supply.

Fixed pitch Examples of machine dialogue (e.g. file contents or screendisplay).

[] Square brackets enclose optional items.

{} Braces enclose a list from which you must choose one item.

| A vertical bar separates the items in a list of choices.

<> Angular brackets:

• either enclose the name of a key on the keyboard.

• or indicate the individual elements in command syntax,filenames, pathname, etc.

... Ellipsis points indicate that you can repeat the preceding itemone or several times.

Preface

40 A2 65CF Rev00 v

Manual Directory

DCE Documentation (delivered on tape with the DCE code)

OSF Introduction to DCE1 ...............................................................................86 A2 30VAOSF DCE User's Guide and Reference1 .........................................................86 A2 31VAOSF DCE Application Development Guide1 ....................................................86 A2 32VAOSF DCE Application Development Reference1 .............................................86 A2 33VAOSF DCE Administration Guide1 .....................................................................86 A2 34VAOSF DCE Administration Reference1 ..............................................................86 A2 35VADPX20 DCE Message Reference Guide2...................................................... 86 A2 48WGDPX20 DCE GDS Administration guide and Reference2.............................. 86 A2 86WGDPX20 DCE Administration Guide..................................................................86 A2 98WEDPX20 DCE Overview2.................................................................................. 86 A2 00WG

GCOS DCE Documentation

GCOS DCE - Overview....................................................................................40 A4 61CFDCE RPC on GCOS7 Administration Guide ....................................................40 A2 62CFDCE RPC on GCOS7 Software Release Bulletin ............................................40 A2 65CFDCE RPC on GCOS8 Administration Guide .................................................... 67 A2 LZ96DCE RPC on GCOS8 Software Release Bulletin ............................................67 A2 SH24DCE RPC Ally Administrative Supplement.......................................................40 A2 64CF

GCOS 7 Documentation

GCOS7 System Overview............................................................................... 47 A2 04UGTDS Administrator's Guide...............................................................................47 A2 20UTGCOS7 System Operator's Guide .................................................................. 47 A2 60UUGCOS7 Error Messages and Return Codes Directory .................................... 47 A2 10UJGCOS7 Console Messages ............................................................................ 47 A2 61UU

1 Manual also available from Prentice Hall

2Paper copy delivered with the software


vi 40 A2 65CF Rev00

OPEN7 Documentation

TCP/IP7 End User's Guide...............................................................................47 A2 30USOPEN7 Administrator's Reference Manual ......................................................47 A2 31USOPEN7 Administrator's Guide..........................................................................47 A2 32US

GCOS 8 Documentation

Workstation Command Language Reference Manual .................................... 67 A2 DH32TP8 Programmer's Guide................................................................................ 67 A2 DH33TP8 Administrator's Guide .............................................................................. 67 A2 DH36Sockets Programmer's Guide ..........................................................................67 A2 LC02Virtual C Language User's Guide.....................................................................67 A2 LC38

40 A2 65CF Rev00 vii

Contents

1 General Release Information....................................................... 1-1

1.1. INTRODUCTION.................................................................................................... 1-1

1.2. ASSOCIATED SOFTWARE .................................................................................. 1-1

2 Installation Instructions ............................................................... 2-1

2.1. DELIVERABLES.................................................................................................... 2-1

2.2. DELIVERY PACKAGE........................................................................................... 2-1

2.3. DELIVERY MECHANISM ...................................................................................... 2-2

2.4. INSTALLATION MECHANISM.............................................................................. 2-3

2.5. MESSAGES FOR THE INSTAL JOB.................................................................... 2-4

2.6. PATCHES REQUIRED FOR DCE RPC ON GCOS7 ............................................ 2-4

2.7. PROBLEMS IDENTIFIED...................................................................................... 2-5

2.8. EXECUTION OF TESTS PROVIDED BY GX-RPC7............................................. 2-5


viii 40 A2 65CF Rev00

3 Maintenance and Debugging....................................................... 3-1

3.1. PROBLEM REGISTRATION................................................................................. 3-1

3.2. MAINTENANCE..................................................................................................... 3-1

3.3. DEBUGGING ......................................................................................................... 3-1

3.4. TRACE OPTION ON OPEN7 ................................................................................ 3-2

3.5. ANOMALIES IN THE SOCKET_SERV/HSL CONTEXT....................................... 3-3

3.5.1. Abort of a process................................................................................................ 3-3

3.5.2. OPEN7 is terminated due to administrator action ............................................ 3-3

3.5.3. Abort of socket_serv............................................................................................ 3-4

3.5.4. Abort of OPEN7 .................................................................................................... 3-4

4 Ally Information ............................................................................ 4-1

4.1 STATUS................................................................................................................. 4-1

4.2 ALLY CONTROLLED ACCESS TO CDS NAMES ............................................... 4-1

4.3 ALLY TRACES ...................................................................................................... 4-2

40 A2 65CF Rev00 1-1

1. General Release Information

1.1. INTRODUCTION

This Software Release Bulletin (SRB) provides installation instructions for DCE RPC onGCOS7. The software is based on the Open Software Foundation's (OSF) DistributedComputing Environment (DCE). DCE makes development of distributed applicationsindependent of the underlying network topology and of hardware and software platforms.

DCE RPC on GCOS7 adds new capabilities to GCOS7 systems by rendering servicesimplemented on UNIX accessible to applications on GCOS7. For a complete descriptionof the part DCE RPC on GCOS7 plays in Bull's Integration into DCE offer, refer to GCOSDCE - Overview.

DCE RPC on GCOS7 is delivered on a tape labelled GXRPC7 which must be installed asindicated in section "Installation Instructions". Additional information about theconfiguration of the DCE RPC on GCOS7 processing environment can be found in DCERPC on GCOS7 Administration Guide.

1.2. ASSOCIATED SOFTWARE

DCE RPC on GCOS7 operates in association with the following software:

• the sub-system OPEN7 1.9.3.1 with the TCP/IP7 communications software must beavailable on each DPS7000 on which an RPC client will run,

• the Technical State TS6152 (at least) is required for the GCOS7 part of RPC onGCOS7.

• deported ALLY (version 1.2.1) functions are required on a DPX20/AIX (at least theversion AIX 3.2.5) in the network (if CDS is to be used),

• DCE (at least the version 1.2 on AIX 3.2.5) is required for the server part of distributedapplications,

• an IDL compiler and the UUIDGEN utility are required on a UNIX machine forproducing client and server applications,


1-2 40 A2 65CF Rev00

40 A2 65CF Rev00 2-1

2. Installation Instructions

This section describes the administrative instructions that must be performed to establishthe proper processing environment for DCE RPC on GCOS7 operations.

2.1. DELIVERABLES

• 2 executables socket_serv daemon and socket_stop on OPEN7,

• rpctool on the ALLY machine and on OPEN7 (transforms files generated by the IDLcompiler for use on GCOS7),

• 1 LKU H_RPC_ADAP in the standard SM H_SM10,

• 2 LKUs in the SM H_SM_DCM in a private system (SYS.DCM.SYSTEM),

- H_RPC_DCE- H_RPC_COMMON

• "includes " required for compilation of application programs inSYS.DCM.RPC.INCLUDE library,

• specific GCOS7 "includes " in SYS.DCM.RPC.INCLUDE library.

2.2. DELIVERY PACKAGE

The delivery package consists of :

• DCE RPC on GCOS7 Administration Guide,

• a magnetic tape marked GXRPC7.


2-2 40 A2 65CF Rev00

The contents of the magnetic tape are:

• INSTAL : JCL for installation of GX-RPC7,

• SYS.DCM.SYSTEM: SM of the GX-RPC7 run-time package,

• SYS.DCM.RPC.INCLUDE: "Include " structures for the API,

• SYS.DCM.RPC.TESTSL: Objects for tests and diagnostics,

• SYS.DCM.RPC.TESTLM: Load Modules for running tests and diagnostics.

2.3. DELIVERY MECHANISM

The DCE RPC on GCOS7 deliverables will be sent to the customer on magnetic tape, andshould be installed by the system administrator as indicated below.

On GCOS7 :

• The private SM (H_SM_DCM) will be available in SYS. DCM. SYSTEM.

• All include files (DCE RPC includes and specific GCOS7 includes ) will be available inthe library SYS.DCM.RPC.INCLUDE.

On OPEN7 :

The 2 executables socket_serv and socket_stop are components of OPEN7. They areplaced in the /etc directory. Execution is reserved for root.

rpctool (which provides automatic modification of IDL-generated code for use onGCOS7) . It is located in the directory /usr/bin.

On ALLY (DPX20) :

rpctool . It is located in the directory /usr/bin.

Installation Instructions

40 A2 65CF Rev00 2-3

2.4. INSTALLATION MECHANISM

To install DCE RPC on GCOS7:

1 Log onto IOF under the SYSADMIN project.

2 Enter:

EJR INFILE=INSTAL:GXRPC7:MT

This job will initiate the following dialogue :

aa/Enter input tape media name [default GXRPC7]

REP aa(tape media name is GXRPC7 by default)

bb/Enter input tape device type [default MT/9]

REP bb

cc/Enter disk media name where file SYS.DCM.SYSTEM is or is to belocated

REP cc <media-name>

• name of disk where file SYS.DCM.SYSTEM is to be created and down-loaded from thedelivery tape for the first time

• name of disk where an existing SYS.DCM.SYSTEM is located for a replacement of itscontents with a later version from the tape

dd/Enter its device type (D500 B10 FSA)

REP dd B10device type of the above media (must belong to the list)

ee/Enter disk media name where other GXRPC7 libraries are or areto be located

REP ee <media-name>

• name of disk where the libraries

- SYS.DCM.RPC.INCLUDE- SYS.DCM.RPC.TESTSL- SYS.DCM.RPC.TESTLM

... are to be created and down-loaded for a first-time installation

• name of disk where the existing libraries are located for the replacement of theircontents with later versions from the tape.


2-4 40 A2 65CF Rev00

ff/Enter its device type (D500 B10 FSA)

REP ff B10device type of the above media (must belong to the list)

2.5. MESSAGES FOR THE INSTAL JOB

On normal completion:

**** Creation of SYS.DCM.SYSTEM and . . . . .******** Loading of H_SM_DCM onto BKST . . OK ******** Installation of RPC product . . . . . . . . OK ****

Error messages:

*** Error while allocating SYS.DCM.SYSTEM ****** Error while restoring SYS.DCM.SYSTEM from tape ****** Error while replacing RPC LKUs on SYS.DCM.SYSTEM ****** Error while loading H_SM_DCM onto BKST ****** Error while preallocating SYS.DCM.RPC.INCLUDE ****** Error while restoring SYS.DCM.RPC.INCLUDE from tape ****** Error while preallocating SYS.DCM.RPC.TESTSL ****** Error while restoring SYS.DCM.RPC.TESTSL from tape ****** Error while preallocating SYS.DCM.RPC.TESTLM ****** Error while restoring SYS.DCM.RPC.TESTLM from tape ***

All error messages are followed by :

*** See JOR and JOBOUT for more details ***

2.6. PATCHES REQUIRED FOR DCE RPC ON GCOS7

1 The 'C' compiler option K47=Y is required for certain source files. This option wasprovided specifically for GX-RPC7 by the following SERs :

• L8493 (H_SM17 in H_CCG)• L8793 (H_CL)

These are available in the standard version of GCOS7 V6 TS 6152.

2 JOBM must call an RPC initialization function at each system restart. The SERM0903 (H_NUCLEUS) is required to effect this function call. This call will beavailable in the standard version of GCOS7 V6 TS 6254.

3 JOBM must call a GX-RPC7 purge function at the end of each step. The SER L8043(LKUZ , H_JOB_LKUZ ) is required to effect this function call. This call will beavailable in the standard version of GCOS7 V6 TS 6254.

4 The IDL "broadcast" attribute was not supported. This problem is solved with SERsM2322 and M2847.

Installation Instructions

40 A2 65CF Rev00 2-5

2.7. PROBLEMS IDENTIFIED

1 Some problems have been detected in the conversion routines used when dealingwith char data. Two characters :

• Newline = `\n' (EBCDIC code = 0X15),• Pipe = `|' (EBCDIC code = 0X6A).

are not correctly converted to ASCII (and conversely) by the OSF conversion tables.This problem must be solved both in :

• server applications running on DPX20,• client applications running on GCOS7.

2 The number of I/O operations effected on OPEN7 has been shown to be high whena TDS/RPC load test is run.

3 rpctool (current version): does not use -cstub, -caux, -header options of the IDLcompiler, if rpctool used on the ALLY machine (transforms IDL-generated files foruse on GCOS7 with standard names: interf_cstub.c , interf_caux and interf.h )).

2.8. EXECUTION OF TESTS PROVIDED BY GX-RPC7

Refer to section 3, sub-section "Test and diagnostics" in the document DCE RPC onGCOS7 Administration Guide.


2-6 40 A2 65CF Rev00

40 A2 65CF Rev00 3-1

3. Maintenance and Debugging

3.1. PROBLEM REGISTRATION

All software problems are reported using Software Technical Action requests (STARs) viathe Bull OSCAR system. Please report all problems you meet to your local Bull CustomerSupport organisations.

3.2. MAINTENANCE

The following means will be used for error correction in the code :

• run-time package of GX-RPC7 : patch in SYS.DCM.SYSTEM or source correction,

• pseudo-socket maintenance : patch in H_SM10,

• socket_serv maintenance on OPEN7 : source correction,

• Ally maintenance : source correction on AIX,

• server part maintenance : DCE problem reports to the OSF organisation.

3.3. DEBUGGING

No on-line trace on GCOS7 (DEBUG compilation) is supported.

DCE RPC on GCOS7 Software Release Bulletin

3-2 40 A2 65CF Rev00

3.4. TRACE OPTION ON OPEN7

By default, socket_serv does not trace any event.

In OPEN7 startup, socket_serv is started without trace, in the form:

socket_serv 1>>/tmp/socket_sv.err 2>>/tmp/socket_sv.err

When you need events tracing:

1 retrieve socket_serv pid (socket_serv child pid)

• either use ls_attach : in first line for RPC_SH_MEM_01, pid is indicated.• or use "ps -edf | grep socket_serv " : take into account child pid.

2 write your trace_level (0,1,2,3 or 4, see below) in the file /etc/rpc_level (with ed orvi ).

3 send a signal with "kill -16 pid ". When socket_serv receives this signal, it will read/etc/rpc_level and modify the trace_level dynamically.

When you want to stop tracing:

1 write 0 in /etc/rpc_level

2 send signal 16 (SIGUSER1) to socket_serv .

If socket_serv has been stopped by socket_stop , you may start it again with a commandof the form:

socket_serv trace_level 1>>/tmp/socket_sv.err 2>>/tmp/socket_sv.err

trace_level value =

0 No trace

1 All functions (such as socket , bind , gethostbyname ,sendto , recvfrom .. ) that "transit" via the HSL segmentRPC_SH_MEM_XX are traced, with an indication of theGCOS7 process submitter, buffer length (pertinentinformation for sendto , recvfrom .. ), ..

2 In addition to level1 trace, buffers are printed for the functionssendto , recvfrom , sendmsg , recvmsg , read_tcp ,write_tcp .

3 In addition to level1 trace, details are printed for the functionssocket , close_socket , closeall (close_socket for aprocess), close_pg (close_socket for a process- group).These details include the number XX of the HSL segmentRPC_SH_MEM_XX used, an indication of the descriptorreturned by the socket function,..

Maintenance and Debugging

40 A2 65CF Rev00 3-3

4 In addition to level1 trace, the start of buffers are printed forthe functions sendto , recvfrom , sendmsg , recvmsg ,read_tcp , write_tcp . 96 bytes are printed, i.e. HEADER (80bytes) and 16 bytes.

other ---> error message:

"RPC trace_level must be in the range 0 to 4,trace is reset"

... and socket_serv will continue without tracing.

3.5. ANOMALIES IN THE SOCKET_SERV/HSL CONTEXT

3.5.1. Abort of a process

Abort of a process with the message:

"RPC warning: check that HSL and socket_serv are running"

Verify that OPEN7 is running:

• If not, start OPEN7. In fact, the load module H_HSL will be launched on GCOS7 too ifnot already started, and then socket_serv will be launched.

• if yes, verify that the Load-Module H_HSL is running:

- If not, launch it (maintain HSL (MNHSL) on GCOS7), and launch socket_serv onOPEN7.

- if yes, launch socket_serv on OPEN7 in background mode.

3.5.2. OPEN7 is terminated due to administrator action

socket_serv is terminated in OPEN7 shutdown, by launching socket_stop . The Load-Modules H_HSL continue on GCOS7. Current "pseudo_sockets " calls are abnormallyterminated. Subsequent "pseudo_sockets " calls will obtain the return value -1 and aspecific errno of socklib.

When OPEN7 starts again, socket_serv will be launched automatically (it is part ofOPEN7 startup). Then "pseudo_sockets " calls will be possible again.


3-4 40 A2 65CF Rev00

3.5.3. Abort of socket_serv

For example, due to a command " kill -9 " on socket_serv process submitted by root.

Other signals don't lead to process abort. The Load-Module H_HSL continues onGCOS7. Current "pseudo_sockets " calls are abnormally terminated. Processes arenever "blocked" on semaphores. Subsequent "pseudo_sockets " calls will obtain themessage:

"RPC warning: check that HSL and socket_serv are running".

Launch socket_serv . Then "pseudo_sockets " calls will be possible again.

NOTE: This is not the normal way to stop socket_serv . You should normally stop itwith the socket_stop command.

3.5.4. Abort of OPEN7

The Load-Module H_HSL continues on GCOS7. Current "pseudo_sockets " calls areabnormally terminated. Processes are never "blocked" on semaphores. Subsequent"pseudo_sockets " calls will obtain the message:

"RPC warning: check that HSL and socket_serv are running"

When OPEN7 starts again, socket_serv will be launched automatically (it is part ofOPEN7 startup). Then "pseudo_sockets " calls will be possible again.

40 A2 65CF Rev00 4-1

4. Ally Information

4.1 STATUS

utc_adjtime() kills the Ally. The time service (DTS) is not supported.

The signals SIGILL, SIGTRAP, SIGIOT, SIGEMT, SIGFPE, SIGBUS, SIGSEGV,SIGSYS, SIGPIPE are not visible to the Ally (new in AIX 3.2.5). The Ally is not able to becloned in case of a problem.

In some cases dnsReadAttrValue() returns false information. But all the NSI tests workcorrectly.

4.2 ALLY CONTROLLED ACCESS TO CDS NAMES

The Ally can access, on behalf of GCOS7, the CDS names which need access control.The administrator must create an account for the Ally, at configuration time, using smit .

The characteristics of the Ally are:

Principal: allyGroup: allyOrganisation: GCOS-DCEaccount: ally

GCOS7 accesses to CDS will be made with the access rights of the account "ally". Referto the OSF DCE Administration Guide, chapter 7 "Controlling Access to CDS names" forfurther information.


4-2 40 A2 65CF Rev00

4.3 ALLY TRACES

The Ally may optionally output a trace.

To set the Ally trace level and select the destination file, enter:

smit allyconf_hdr

To switch the trace on and off (once the Ally is running), enter:

smit allytrace

This command also allows you to read the traces of the Ally while it is running.

For more information, use smit's context help for more information. Enter:

smit ally

Note that despite what the help says, /etc/rc.ally does not switch the trace off at boottime. If you set a debug level different from 'none', the Ally will output the trace as soon asit is launched.

Under normal conditions, you may want to set the trace to 'maximum' and then switch thetrace off until you need it with smit allytrace .

Technical publication remarks form

Title : DPS7000/XTA NOVASCALE 7000 DCE RPC ON GCOS 7 Software ReleaseBulletin Distributed Computing

Reference Nº : 47 A2 65CF 00 Date: April 1994

ERRORS IN PUBLICATION

SUGGESTIONS FOR IMPROVEMENT TO PUBLICATION

Your comments will be promptly investigated by qualified technical personnel and action will be taken as required.If you require a written reply, please include your complete mailing address below.

NAME : Date :

COMPANY :

ADDRESS :

Please give this technical publication remarks form to your BULL representative or mail to:

Bull - Documentation Dept.

1 Rue de ProvenceBP 20838432 ECHIROLLES [email protected]

Technical publications ordering form

To order additional publications, please fill in a copy of this form and send it via mail to:

BULL CEDOC357 AVENUE PATTONB.P.2084549008 ANGERS CEDEX 01FRANCE

Phone: +33 (0) 2 41 73 72 66FAX: +33 (0) 2 41 73 70 66E-Mail: [email protected]

CEDOC Reference # Designation Qty

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

[ _ _ ] : The latest revision will be provided if no revision number is given.

NAME: Date:

COMPANY:

ADDRESS:

PHONE: FAX:

E-MAIL:

For Bull Subsidiaries:

Identification:

For Bull Affiliated Customers:

Customer Code:

For Bull Internal Customers:

Budgetary Section:

For Others: Please ask your Bull representative.

BULL CEDOC

357 AVENUE PATTON

B.P.20845

49008 ANGERS CEDEX 01

FRANCE

47 A2 65CF 00REFERENCE

DCE RPC ON GCOS 7 - Bull On-line Support...

Documents

Transcript of DCE RPC ON GCOS 7 - Bull On-line Support...