Considerations for system tuning during error recovery

You can also sort the WRKPRB display by the date the problem was entered into the log.

Note: Use the WRKPRB command for the menu options, additional problem analysis, or documenting problem records.

Solving communication problems using status information

You can often diagnose the communications problem by checking communications status. Status information for network servers, network interfaces, lines, controllers, or devices may represent the symptom of the problem.

To check and change the communication configuration on the system, do the following:

1.Type the Work with Configuration Status (WRKCFGSTS) command on any AS/400 command line.

2.Press F4. The Work with Configuration Status display appears.

3.Specify the configuration type for the CFGTYPE parameter.

4.Specify the configuration description for the CFGD parameter.

Note: You may subset this list produced by WRKCFGSTS based on the status of the objects using the STATUS parameter. For example, if you want to see just the failed objects, specify STATUS(*FAILED).

Considerations for system tuning during error recovery

The overall performance tuning that is done by the system can play a significant role during error recovery scenarios. For example, you may need to change the machine pool if it is too small because it can cause excessive error recovery times.

vPerformance Adjustment – QPFRADJ

The automatic performance adjustment function of the system is set to 2 when the system is shipped. The system can automatically adjust the performance of the system based on this value. Automatic adjustment may be a desirable feature, particularly when unexpected loads hit the system. Automatic adjustment can help the system perform better through these peak loads.

vSubsystem considerations

You should consider dividing communications users (whether they are remote workstation or APPC communication users) into multiple subsystems. If communications fails, all users who are in a single subsystem may be affected as a result of the communications recovery that is performed on their systems. For more information, see:

– “Considerations for subsystem configuration for error recovery performance” on page 11

Using error messages to aid in error recovery

When problems occur in communications, there are many places you can look for error messages and additional information to help resolve the problems. See the topics below for the most common places to look for APPC error information.

vMessages queues, see “Displaying message queues to solve communication problems” on page 79

vJob logs, see “Job logs and communication problems” on page 80

vOther logs, see “Displaying the Product Activity Log to solve communication problems” on page 80 and “Displaying the Print Error Log to solve communication problems” on page 80

vStart Service tools, see “System service tools and communication problems” on page 82

vCommunications trace, see “Solving communication problems using communications trace” on page 81

Solving communication problems using reason codes

When the local system rejects an incoming program start request, a message is sent to the system operator message queue. You can use the message information to determine why the program start request was rejected.

84Version 5

AS/400 specifications

The IBM AS/400, now known as the IBM iSeries, is a midrange computer system that has been a cornerstone of enterprise computing since its introduction in 1988. Designed to provide a robust platform for business applications, the AS/400 is celebrated for its reliability, scalability, and integrated database capabilities.

One of the key features of the AS/400 is its Integrated Operating Environment, which blends hardware and software resources seamlessly. This integration allows businesses to execute diverse workloads, ranging from traditional applications to modern web-based services, all on a single platform. The operating system, OS/400 (now IBM i), offers a rich set of APIs and tools for developers, simplifying application development and management.

Another standout characteristic of the AS/400 is its built-in database, DB2 for i. This powerful relational database management system allows for efficient data handling and provides advanced features such as support for SQL, XML, and JSON, making it easier for businesses to manage their data and integrate it with other systems. The database's tight integration with the operating system enables high performance and security.

In terms of scalability, the AS/400 can accommodate small businesses as well as large enterprises, with the ability to support hundreds of users simultaneously. Its architecture allows for easy upgrades in hardware, meaning that organizations can scale their systems without replacing the entire infrastructure.

Security is another critical attribute of the AS/400. With a sophisticated security model, it offers built-in user authentication, access control, encryption, and auditing capabilities to protect data and applications from unauthorized access.

The AS/400 also supports multiple programming languages, including RPG, COBOL, Java, and PHP, giving organizations the flexibility to choose the development tools that best fit their needs. This diversity helps maintain legacy applications while also developing new ones that leverage modern technologies.

Moreover, the platform supports both traditional green-screen interfaces and modern graphical user interfaces, allowing organizations to transition smoothly into contemporary user experience paradigms.

Overall, the IBM AS/400 stands out as a resilient, flexible, and secure computing platform that enables organizations to effectively manage their business operations, streamline processes, and adapt to changing market demands. Its unique combination of integrated features and capabilities ensures that it remains relevant in today's fast-paced technology landscape.