HPlogo LU 6.2 API Application Programmer's Reference Manual: HP 3000 MPE/iX Computer Systems > Chapter 5  Intrinsic Descriptions

MCGetAttr

» 

Technical documentation

Complete book in PDF
» Feedback

 » Table of Contents

 » Glossary

 » Index

Returns information pertaining to the specified conversation.

Syntax

			             I16V       I32            CA
								MCGetAttr(ResourceID, Status, [OwnFullyQualifiedLUName],
 
						                CA                    CA
								          [PartnerLUName], [PartnerFullyQualifiedLUName],
 
 
							              CA         I16
						          [ModeName], [SyncLevel]);

Parameters

ResourceID

Required; 16-bit signed integer by value; input. This is the unique resource ID number assigned to this conversation when it was allocated. See MCAllocate or MCGetAllocate, in this chapter, for more information.

Status

Required; 32-bit signed integer; output. Indicates the result of intrinsic execution. See the "Status Parameter" section, earlier in this chapter, for more information.

OwnFullyQualifiedLUName

character array; output. If the specified conversation is using a dependent LU to communicate with a Type 5 node (like an IBM mainframe), this parameter is not implemented and returns a 17-character array of blanks.

If the specified conversation is using an independent LU on MPE XL to communicate with a Type 2.1 node (like an IBM AS/400), this is a 17-character array that returns the fully qualified LU name of the local LU. It has the form NetID.LUName, where NetID and LUName are the names of the local SNA network and the local LU configured in the APPC subsystem configuration. See the APPC Subsystem on MPE XL Node Manager's Guide for information on APPC subsystem configuration.

PartnerLUName

character array; output. This is an 8-character ASCII array, left justified and padded with blanks. It returns the name of the remote LU used by the remote TP. PartnerLUName is the name by which the local LU knows the remote LU. PartnerLUName is returned only on a conversation using a dependent LU to communicate with a Type 5 node (like an IBM mainframe).

PartnerFullyQualifiedLUName

character array; output. If the specified conversation is using a dependent LU to communicate with a Type 5 node (like an IBM mainframe), this parameter is not implemented and returns a 17-character array of blanks.

If the specified conversation is using an independent LU on MPE XL to communicate with a Type 2.1 node (like an IBM AS/400), this is a 17-character array that returns the fully qualified LU name of the LU used by the remote TP. It has the form NetID.LUName, where NetID is the name of the SNA network where the remote node resides, and LUName is the local name for the remote LU configured in the APPC subsystem configuration. See the APPC Subsystem on MPE XL Node Manager's Guide for information on APPC subsystem configuration. PartnerFullyQualifiedLUName is returned only on conversations using independent LUs.

ModeName

character array; output. This is an 8-character array, left justified and padded with blanks. It returns the mode name configured for the APPC session on which the conversation is allocated. This parameter matches the mode name configured for the SessionType specified in the call to MCAllocate or MCGetAllocate. For more information on mode configuration, see the LU 6.2 API/V Node Manager's Guide or the APPC Subsystem on MPE XL Node Manager's Guide.

SyncLevel

16-bit signed integer; output. The synchronization level (whether or not confirmation is used) established for this conversation. Possible values are as follows:

0 = CONFIRM

Denotes that the MCConfirm and MCConfirmed intrinsics can be called. It also means that the confirm request option of any intrinsic may be used.

2 = NONE

Denotes that no confirmation will be used. If the SyncLevel is 2, the MCConfirm and MCConfirmed intrinsics cannot be called during this conversation, nor can the confirm request option of any intrinsic be used during this conversation.

Description

This intrinsic allows the local TP to get information about the conversation specified in the ResourceID parameter.

Status Info Values

 0    Successful Completion.
-1    Intrinsic called with parameter out of bounds.
-2    Invalid 'ResourceID' parameter specified in intrinsic call.
-20   Not enough stack space for intrinsic to run.
-90   An internal error in Presentation Services has occurred.
-91   An internal error in the APPC subsystem has occurred.
-1002 An internal error at the mapped conversation level has occurred.
-1003 Required parameter missing.
Feedback to webmaster