User manual PROGRESS DELPH.855

[. . . ] The references in this manual to specific platforms supported are subject to change. A (and design), Actional, Actional (and design), Affinities Server, Allegrix, Allegrix (and design), Apama, Business Empowerment, ClientBuilder, ClientSoft, ClientSoft (and Design), Clientsoft. com, DataDirect (and design), DataDirect Connect, DataDirect Connect64, DataDirect Connect OLE DB, DataDirect Technologies, DataDirect XQuery, DataXtend, Dynamic Routing Architecture, EasyAsk, EdgeXtend, Empowerment Center, eXcelon, Fathom, IntelliStream, Neon, Neon New Era of Networks, O (and design), ObjectStore, OpenEdge, PDF, PeerDirect, Persistence, Persistence (and design), POSSENET, Powered by Progress, PowerTier, ProCare, Progress, Progress DataXtend, Progress Dynamics, Progress Business Empowerment, Progress Empowerment Center, Progress Empowerment Program, Progress Fast Track, Progress OpenEdge, Progress Profiles, Progress Results, Progress Software Developers Network, ProVision, PS Select, SequeLink, Shadow, ShadowDirect, Shadow Interface, Shadow Web Interface, ShadowWeb Server, Shadow TLS, SOAPStation, Sonic ESB, SonicMQ, Sonic Orchestration Server, Sonic Software (and design), SonicSynergy, SpeedScript, Stylus Studio, Technical Empowerment, Voice of Experience, WebSpeed, and Your Software, Our Technology-Experience the Connection are registered trademarks of Progress Software Corporation or one of its subsidiaries or affiliates in the U. S. AccelEvent, Apama Dashboard Studio, Apama Event Manager, Apama Event Modeler, Apama Event Store, AppsAlive, AppServer, ASPen, ASP-in-a-Box, BusinessEdge, Cache-Forward, DataDirect Spy, DataDirect SupportLink, DataDirect XML Converters, Future Proof, Ghost Agents, GVAC, Looking Glass, ObjectCache, ObjectStore Inspector, ObjectStore Performance Expert, Pantero, POSSE, ProDataSet, Progress ESP Event Manager, Progress ESP Event Modeler, Progress Event Engine, Progress RFID, PSE Pro, SectorAlliance, SmartBrowser, SmartComponent, SmartDataBrowser, SmartDataObjects, SmartDataView, SmartDialog, SmartFolder, SmartFrame, SmartObjects, SmartPanel, SmartQuery, SmartViewer, SmartWindow, Sonic, Sonic Business Integration Suite, Sonic Process Manager, Sonic Collaboration Server, Sonic Continuous Availability Architecture, Sonic Database Service, Sonic Workbench, Sonic XML Server, The Brains Behind BAM, WebClient, and Who Makes Progress are trademarks or service marks of Progress Software Corporation or one of its subsidiaries or affiliates in the U. S. Java and all Java-based marks are trademarks or registered trademarks of Sun Microsystems, Inc. [. . . ] User selected name of a value data key that is only used with keyed value sets. Valid value key names are from 1 to 48 bytes in length and must be composed of the same characters used for valid set names (that is, valid key names must begin with an alphabetic character and contain only alphanumeric or underscore characters). Positive integer corresponding to the nth value data key (used only with keyed value sets). Positive integer corresponding to the nth state information set known to the application. Indicates that any trailing name suffix(es) are valid for use with a non-indexed GLVSTATE. setname. Reference can also be used in this position for indirect indexed access. keyindex setindex <suffix> The GLVSTATE variable symbol cannot exceed 84 bytes in length, including all qualifiers. Shadow z/Enterprise Web Server Administration Guide 9-9 Automated State Management Facility (ASMF) Note: It is impossible to use both the maximum size "setname" and the maximum size "keyname" for most, otherwise valid, symbol name combinations. Collection Control Variable Name An information set's control variable is the primary means of controlling the set or determining whether a set exists. The control variable name follows: GLVSTATE. setname where setname is the application-assigned name of the state information set. Evaluation of "GLVSTATE. setname" When you interrogate the value of an information set's control variable, one of the following two status values is returned. (These are the only two values that are ever returned, even if the query is made by a REXX-language procedure against a previously unknown or uninitialized variable. ) NULL A NULL (zero-length) string is returned if the value information within this set is unusable. For example, if the set does not exist (UNKNOWN status) or if it is associated with an expired server-side token (EXPIRED status), this value will be returned as an overall indication that the set is unusable. VALID This string is returned only if the state information within the set is usable by the application. For example, it is returned for sets that have either an ACTIVE or RESTORED status. Pre-Defined "GLVSTATE. setname" Values By assigning a pre-defined value to a set's control variable, the underlying state information set is created, deleted, or re-initialized. A RESTORED set was reset. For cookie-based sets, HTTP "Set-cookie:" response headers are generated automatically by the server when outbound transmission buffers are flushed to the client. RESTORED This string is returned for any state information set that has been successfully re-created by the server using inbound query or cookie information. All value data, originally saved in the set when it was created, is usable by the application. 9-12 Shadow z/Enterprise Web Server Administration Guide Using COOKIE-Type Information Sets Table 9­5. Variable Values for "GLVSTATE. setname. STATUS" Variable Value EXPIRED Description This string is only returned for token-based information sets. Inbound query or cookie variables processed by the server contain a server-side token ID. Because the token has expired, all value data originally saved in the set when it was created is no longer available. Evaluation of "GLVSTATE. setname. TYPE" When you interrogate the value of the "GLVSTATE. setname. TYPE" variable, a COOKIE, CTOKEN, or FTOKEN value is returned. Note: The COOKIE, CTOKEN, or FTOKEN values are only returned for information sets that are known to the server. For unknown sets, one of the following will be returned: For high-level language callers, a null string is returned. For REXX-language callers, a string containing the name of the variable corresponding to the REXX-language specification for the handling of uninitialized variables will be returned. Evaluation of "GLVSTATE. setname. TOKENID" When you interrogate the value of the "GLVSTATE. setname. TOKENID" variable, the server-side token ID value (CTOKEN and FTOKEN) is returned. Information sets are returned and displayed as 24-byte, hexadecimal values, unique from all other serverassigned token ID values. Note: For cookie-based and unknown sets, one of the following will be returned: For high-level language callers, a null string is returned. For REXX-language callers, a string containing the name of the variable corresponding to the REXX-language specification for the handling of uninitialized variables will be returned. Using COOKIE-Type Information Sets HTTP cookies are used as the communications transport for application state information and application information in encoded form. They are transmitted directly to and from the client. Shadow z/Enterprise Web Server Administration Guide 9-13 Automated State Management Facility (ASMF) How Cookies Work Prerequisites 1. [. . . ] The assignment of subnets can be done locally, while the whole network still appears to be one IP network to the outside world. Network Interface Layer This layer, sometimes referred to as the link layer, data link layer, or network layer, is implemented by the physical network which connects the computers. Although this layer is not covered by the TCP/IP standards, there are specific methods used to access higher layers. The following are the different types of networks which the Internet layer can be connected. Multiaccess broadcast networks Here, any system (TCP/IP host) can have multiple connections to other hosts simultaneously, plus it can send information to all other hosts on the same network with a single message command. [. . . ]