Cisco Systems S/390 manual Exit Recovery Routine, Recovery Exit Register Contents

Page 12

Documentation

Exit Recovery Routine

The exit program can supply the address of a recovery routine via a parameter returned at the INIT exit point. The exit facility calls this routine in the event of an ABEND in the exit program. The recovery routine is called in the same mode as the ABENDing exit program, and is passed the System Diagnostic Work Area (SDWA) address and the EWA address (if any). Since the exit's recovery routine is called after the system's Recovery and Termination Manager (RTM) has finished processing the ABEND, it should perform only local clean-up functions. Any updates to the SDWA are ignored. The recovery routine should not attempt to free the SDWA, since this will be done by the exit facility.

Recovery Exit

Exit Point: When an ABEND has occurred in an exit program.

Function: Perform clean-up associated with the exit program.

Dispatchable Unit: Identical with the ABENDing exit program.

Register contents are shown in the following table.

Table 5

Recovery Exit Register Contents

 

 

Register

Contents on Entry

 

 

R00

SDWA (if processing under an SRB, a copy of the SDWA)

 

 

R01

Exit Work Area address (if applicable)

 

 

R02-R12

Zeros

 

 

R13

Save area address

 

 

R14

Return address

 

 

R15

Entry point address

 

 

On return from the recovery exit, R13 must be restored.

Exit Parameter List Mapping Macro - T00DEXPL

A new macro, T00DEXPL, is supplied to map the parameter lists to the exit program at the various exit points. The macro is distributed in the SAMP library.

12Cisco IOS for S/390 Release 2.0 Release Notes

Page 11 Page 13
Image 12
Page 11 Page 13
Contents Cisco IOS for S/390 Release 2.0 Release Notes Enhanced Features Enhanced FeaturesImproved Performance and Efficiency Improved ManagementProduct Changes Enhanced APIsOther Enhancements Enhanced APIsAPPCFG00 DNRCFG00 IJTCFG00 SNMCFG00 TCPCFG00 Product Changes Parameter AliasesAcpcfg Member Changes Arcb Cbuf Epcb SRE Tpcb Tsqb Tucb Product ChangesProduct Changes New Features New FeaturesCisco Connection Online DocumentationCisco Connection Online Product Documentation Library Product Documentation LibraryService Startup Statement Changes to the Documentation SetCisco IOS for S/390 Users Guide Cisco IOS for S/390 Planning GuideExit Work Area Exit Recovery Routine Recovery ExitRecovery Exit Register Contents Register Contents on EntryCisco IOS for S/390 System Management Guide Customizing CA-ACF2 Version 6 or LaterRefreshing Usstab Syntax DescriptionParameters for the Svcdump Command Protocol Layer Events Subtypes 110 123 DescriptionsMU1IUCV Usermod Correction Subtype DescriptionNetstat RTM Command Cisco IOS for S/390 Customization GuideCapture of User Data in a TLI Trace Tcpeep Netif OptionTCP Mindev and RTO Defaults Changed Recommendations on Setting TOSAppend Keyword for Lupool Statement AppendLogging Keywords Logically Grouped Class Dest Form WriterLines Minutes Sync Logging ExamplesCisco IOS for S/390 Prefixed Messages T01CF080RT01CF081W T01CF082WCisco IOS for S/390 Unprefixed Messages and Codes C24Cxxxx 0Exx T012TOPT Documentation ’C245’ Instance Codes Byte code Description’C24C’ Instance Codes C25Bxxxx 1Dxx T012TERR ’C25B’ Instance CodesC25Fxxxx 21xx T01PSTUB C262xxxx 6Fxx T012TPLKDocumentation Byte code Description XC25F Instance CodesInstalling Cisco IOS for S/390 Release Installation RequirementsCallable System Services Library TSO/EACF/2 SAS/C Release LevelCommon Inet Sockets in OpenEdition RS6000Vtam Release MVS/ESA Release 5.1 ConsiderationsInstallation Process Control File JCLHardware/Software/Microcode Compatibility Installation Process Allocate the Data Set Names for Cisco IOS for S/390 releaseTcpnames JobcardALLOCT00 InstsmpeHolddata SmpecumtGuest bin Cd /pub/ptf520 CustomizationParm Customization Modify Trace on SIZE256Usermod Customization Invoking Cisco IOS for S/390 ReleaseDiagnosis and Problem Reporting Diagnosis and Problem ReportingObtaining GTF Output Obtaining a Snap DumpSAS/C Usage Notes Obtaining a TcpeepObtaining an SVC Dump Obtaining JCL OutputACPCFG00 Host Statement Logstamp Loopbuf MVS Sysdump LoopmtuHost SSN Global API Security Security CLASS, PROFILE, APPLNAME, Xsec LoggingGreetingyesnoappl Logstamp NologstampLUPARMACPLUP00 LUPARMAPPLUP00Service Telnet Appl Termprof FTP GAT Smtp LPR Vtam Service Telnet ApplApplication Statement Mappings TCP Protocol ParametersKEEPALIVETIMERnum TIB ProtocoltcpTADDRUSEranges KeepalivegarbagenogarbageUDP Protocol Parameters RAW Protocol ParametersTIB Protocoludp UDPNetwork Parameters TIB ProtocolrawArptable Lnid Loop Network Medianame Network MetricRoute Parameters Mssoptneversubnet NetalwaysChecksumhostyes OffloadnoDriver Configuration LocalArptable ARP FlagsgnacrcsrcErrorabend Optionsasyncsync Dsmesm Getmainpcore Loopnoloop DocpeocpTracenotrace LniclawLniclaw DEVADDRccuu DEVADDRccuuSinglenoopdoublenoop BUFSIZE1024204330724096Driver Configuration LnihyprTrace Name Lnihypr HyprBcasttrunc Errorabend ArptableserverLnilcs and Lnilink Medianame Autostart PfilterIJTCFG00 Changes Logging Statement Ifsparm PromptnopromptAuth Logging Statement Cisco IOS for S/390 Release 2.0 Release Notes

S/390 specifications

Cisco Systems S/390, also known as IBM's S/390 architecture, is a revolutionary mainframe computing solution that has significantly impacted enterprise computing since its introduction. Though primarily associated with IBM, its integration with Cisco Systems technologies has fostered enhanced networking capabilities, creating a robust platform for organizations to leverage.

One of the most notable features of the S/390 architecture is its scalability. The system is designed to manage workloads efficiently, enabling organizations to scale their operations seamlessly as their requirements grow. This architecture supports an extensive range of applications, from transaction processing to complex data analysis, making it suitable for diverse industries.

The S/390 systems are known for their reliability and resilience. With advanced error detection and correction mechanisms, the architecture minimizes downtime, ensuring that mission-critical applications remain operational. The mainframe's design accommodates redundancy and fault tolerance, reinforcing its reputation as a dependable computing solution.

Moreover, security is a core characteristic of the S/390 infrastructure. It incorporates various security features, such as encryption and robust access control mechanisms, to safeguard sensitive data against unauthorized access and cyber threats. This level of security is particularly critical for industries such as finance, healthcare, and government, where data protection is paramount.

The integration of Cisco networking technologies with the S/390 architecture brings enhanced connectivity and streamlined communication capabilities. Cisco’s advanced routing, switching, and security solutions bolster the mainframe's communication prowess, enabling organizations to create seamless, high-performance networks. This ensures that data flows efficiently between the mainframe and other networked devices.

Additionally, S/390 supports an array of middleware solutions, facilitating better interoperability with modern applications and cloud services. Organizations can take advantage of this flexibility to leverage existing investments in technology while embracing innovative solutions.

In summary, Cisco Systems S/390 embodies a potent combination of scalability, reliability, security, and advanced networking features. Its architecture serves as a cornerstone for enterprise computing, allowing organizations to meet their evolving business needs while maintaining high-performance standards. As businesses increasingly rely on data-driven decision-making, S/390 remains a critical asset for organizations striving for efficiency and innovation in their operations.
Top Page Image Contents