Welcome
Fault Analyzer installation and administration
Enabling Artificial Intelligence enhancements
Configuring the MCP Server
For general information about this enhancement, see fa_ai_mcp.html. Set up the workstation-based MCP server on Windows® to connect external AI assistants to Fault Analyzer via z/OSMF REST APIs.
Configuring local authentication using Windows Credential Manager
To run the Model Context Protocol (MCP) server in local or STDIO mode without exposing RACF passwords in configuration files, store your z/OSMF credentials in Windows® Credential Manager.

What's new in IBM Fault Analyzer for z/OS® V17.1
PDF documentation
About this document
Summary of changes
Using Fault Analyzer
Fault Analyzer installation and administration
- Migrating from an earlier version of Fault Analyzer
- Preparing to customize Fault Analyzer
- Customizing the operating environment for Fault Analyzer
- Using the Fault Analyzer IDIS subsystem
  Fault Analyzer uses a subsystem known as IDIS for services that can otherwise not be performed or which might cause incomplete analysis if not started.
- Modifying your ISPF environment
- Customize Fault Analyzer by using USERMODs
- Customize Fault Analyzer by using an IDIOPTLM configuration-options module
- Setting up history files
  Fault Analyzer requires at least one PDS or PDSE data set to be allocated as a fault history file.
- Setting and changing default options for the site
- Providing compiler listings or Fault Analyzer side files
- Customizing the CICS environment
- Customizing the DB2 environment
- Customizing the IMS environment
- Customizing the Java environment
- Customizing the Fault Analyzer Japanese feature
- Verifying Fault Analyzer customization
- Managing history files (IDIUTIL utility)
  The IDIUTIL batch utility can be used to perform history file management functions, such as listing and deleting history file fault entries.
- Providing application-specific explanations and descriptions
- Maintaining Fault Analyzer
- Disabling Fault Analyzer
- Customizing Fault Analyzer by using user exits
- Installing non-ISPF interfaces to access Fault Analyzer history files
- Enabling Artificial Intelligence enhancements
  - Installing and configuring Abend Intelligence
  - Configuring the MCP Server
    For general information about this enhancement, see fa_ai_mcp.html. Set up the workstation-based MCP server on Windows® to connect external AI assistants to Fault Analyzer via z/OSMF REST APIs.
    - Configuring local authentication using Windows Credential Manager
      To run the Model Context Protocol (MCP) server in local or STDIO mode without exposing RACF passwords in configuration files, store your z/OSMF credentials in Windows® Credential Manager.
Fault Analyzer reference information
Sample customized ISPF interface front-end
Java API to download Fault Analyzer report
The Java™ API downloads a Fault Analyzer report from the host and shows it in Eclipse-based products that are developed in Java.
Technical details for screen size adjustments
Support resources
Accessibility features for Fault Analyzer
Accessibility features assist users who have a disability, such as restricted mobility or limited vision, to use information technology content successfully.
Notices
Glossary

Configuring local authentication using Windows® Credential Manager

To run the Model Context Protocol (MCP) server in local or STDIO mode without exposing RACF passwords in configuration files, store your z/OSMF credentials in Windows® Credential Manager.

Before you begin

Ensure that you have a valid RACF user ID and password with access to z/OSMF REST interfaces on the target mainframe LPAR.

About this task

When running in local single-user mode (server.is-remote=false), the MCP server queries Windows Credential Manager at startup to retrieve your RACF credentials and request an authentication token from z/OSMF. Passwords are never written to disk or configuration files.

Procedure

Use the following format for the credential target name:
- FA:zosmf:your_racf_userid, for example FA:zosmf:JSMITH
Store the credential using either the Windows command line or the Control Panel GUI:
- Command line: Open a command prompt and run cmdkey:
```
cmdkey /generic:FA:zosmf:your_racf_userid /user:your_racf_userid /pass:your_racf_password
```
- Control Panel GUI: Open Credential Manager, select Windows Credentials, click Add a generic credential, and enter the target name, user ID, and password.
Verify that the credential target name matches the zosmf.user property in your server configuration file (application.yml).

Results

The MCP server can now authenticate securely with z/OSMF during local startup without prompting for passwords or storing plain-text credentials.