02.12.2012 Views

OpenVMS Cluster Systems - OpenVMS Systems - HP

OpenVMS Cluster Systems - OpenVMS Systems - HP

OpenVMS Cluster Systems - OpenVMS Systems - HP

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Packets<br />

capturing data, F–26<br />

maximum size on Ethernet, 10–16<br />

maximum size on FDDI, 10–16<br />

transmission window size, G–4<br />

PADRIVER port driver, C–17, C–18<br />

Page files (PAGEFILE.SYS)<br />

created by CLUSTER_CONFIG.COM procedure,<br />

8–1, 8–6<br />

Page sizes<br />

hardware<br />

AUTOGEN determination, A–1<br />

PAKs (Product Authorization Keys), 4–6<br />

PANUMPOLL system parameter, A–13<br />

PAPOLLINTERVAL system parameter, A–13<br />

Partner programs<br />

capturing retransmitted packets, F–34<br />

PASANITY system parameter, A–14<br />

Passwords<br />

See <strong>Cluster</strong> passwords<br />

VMS$PASSWORD_DICTIONARY.DATA file,<br />

5–17, 5–21<br />

VMS$PASSWORD_HISTORY.DATA file, 5–17,<br />

5–21<br />

VMS$PASSWORD_POLICY.EXE file, 5–17,<br />

5–21<br />

PASTDGBUF system parameter, A–8, A–14<br />

PASTIMOUT system parameter, A–14<br />

Paths<br />

specifying preferred for MSCP-served disks,<br />

6–5<br />

PBDRIVER port driver, C–18<br />

PEDRIVER<br />

channel selection, G–1<br />

channel selection and congestion control, G–1<br />

Equivalent Channel Set, G–1<br />

load distribution, G–1<br />

PEDRIVER port driver, 2–2, C–18<br />

congestion control, G–3<br />

HELLO multicasts, G–5<br />

implementing the NISCA protocol, F–4<br />

NISCS_LOAD_PEA0 system parameter, 4–4<br />

preferred channel, G–2<br />

retransmission, F–19<br />

SDA monitoring, F–13<br />

Physical Interconnect protocol<br />

See PI protocol<br />

PIDRIVER port driver, 2–2, C–18<br />

PI protocol<br />

part of the SCA architecture, F–3<br />

PK*DRIVER port driver, 2–2<br />

PMDRIVER port driver, 2–2<br />

PNDRIVER port driver, 2–2<br />

POLYCENTER Console Manager (PCM), 1–9<br />

Port<br />

software controllable selection, 6–5<br />

Port allocation classes<br />

See Allocation classes<br />

Port communications, 1–5, C–17<br />

Port drivers, 1–5, C–17<br />

device error-log entries, C–17<br />

error-log entries, C–24<br />

Port failures, C–18<br />

Port polling, C–17<br />

Port-to-Port Communication protocol<br />

See PPC protocol<br />

Port-to-Port Driver level<br />

See PPD level<br />

Port-to-Port Driver protocol<br />

See PPD protocol<br />

PPC protocol<br />

part of NISCA transport protocol, F–3<br />

PPD level<br />

part of PPD protocol, F–3<br />

PPD protocol<br />

part of SCA architecture, F–3<br />

Preferred channels, G–2<br />

Print queues, 5–1, 7–1<br />

See also Queues and Queue managers<br />

assigning unique name to, 7–5<br />

clusterwide generic, 7–7<br />

setting up clusterwide, 7–4<br />

starting, 7–7<br />

Processes<br />

quotas, 2–14, 10–17<br />

Programs<br />

analyze retransmission errors, F–33<br />

LAN analyzer partner, F–34<br />

LAN analyzer scribe, F–34<br />

LAN analyzer starter, F–33<br />

Protocols<br />

Channel Control (CC), F–3<br />

Datagram Exchange (DX), F–3<br />

PEDRIVER implementation of NISCA, F–4<br />

Physical Interconnect (PI), F–3<br />

Port-to-Port Communication (PPC), F–3<br />

Port-to-Port Driver (PPD), F–3<br />

System Application (SYSAP), F–2<br />

System Communications Services (SCS), F–2<br />

Transport (TR), F–3<br />

Proxy logins<br />

controlling, 5–22<br />

records, 5–22<br />

Q<br />

QDSKINTERVAL system parameter, A–9<br />

QDSKVOTES system parameter, 2–8, A–9<br />

QMAN$MASTER.DAT file, 5–23, 7–2, 7–4<br />

authorization elements, 5–19<br />

Queue managers<br />

availability of, 7–2<br />

clusterwide, 7–1<br />

Index–11

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!