Troubleshooting
Problem
This document provides the CRTSRVCFG parameters to be used in creating all configuration scenarios.
Note: Modem and VPN connection are no longer supported.
Environment
It is highly recommended that systems be up to date on PTF levels.
Diagnosing The Problem
The instructions below are intended to delete any previous service configuration, Point-To-Point profiles, line descriptions and configuration files that remain and re-create it. Include basic steps to force Contact Information change and ESA enablement for Call Home.
Reference to the Resolving the Problem section of this document for details.
Do the following while signed on with a user profile that has *SECOFR authority:
- CHGSRVAGTA ENABLE(*NO)
- DLTSRVCFG
- WRKTCPPTP and delete (4=Remove) any remaining profiles that begin with the letter 'Q'
This command was removed on 7.6 - WRKLIND LIND(Q*) and delete (4=Delete) any remaining lines that have the type of *PPP and begin with the letter 'Q'. Also, delete QESLINE, QTILINE, and Q1PLIN type *SDLC, if exist.
- RMVLNK OBJLNK('/qibm/userdata/os400/universalconnection/*')
An error like 'Requested operation not allowed. Access problem.' might appear. Disregard.
- RMVLNK OBJLNK('/qibm/userdata/os400/serviceagent/Contact.properties')
Might not exist. Disregard if an error. - CHGCNTINF MAILADDR(*SAME *SAME *SAME *SAME *SAME XX *SAME) MEDPTF(*DVDROM)
Where XX is the two-character abbreviation for the country or region, such as US for United States, CA for Canada, SE for Sweden.
- CRTSRVCFG ROLE(*PRIMARY) CNNTYPE(*DIRECT) CNTRYID(*SELECT) STATE(*SELECT)
Select the appropriate country/region and state/province (where the system is physically located) If there is a proxy server involved, specify the appropriate proxy information.
If CPD0A35 is received after running CRTSRVCFG, check the RC related and refer to the CRTSRVCFG/CHGSRVCFG fails with msgCPD0A35: Java exception not handled for user-defined document for usual stuff that could cause the error.
- CHGSRVAGTA ENABLE(*YES)
Resolving The Problem
Additional details regard the CRTSRVCFG command
Creating a Direct Internet Connection for the Local System
To create a direct internet connection for only the local system, type the following:
CRTSRVCFG ROLE(*PRIMARY) CNNTYPE(*DIRECT) CNTRYID(*SELECT) STATE(*SELECT) CNNPNT(*NO)
To create a Direct connection for only the local system with a Proxy, type the following:
CRTSRVCFG ROLE(*PRIMARY) CNNTYPE(*DIRECT) CNTRYID(*SELECT) STATE(*SELECT) CNNPNT(*NO) PROXY(XXXXXX *IBMSVR *TRYAFTER UUUUU (PPPPP))
Where XXXXXX is the TCP/IP address of the proxy, *IBMSVR is the port data, *TRYAFTER is the relative priority, UUUUU is the proxy user ID, and PPPPP is the proxy password. Press the Enter key.
1. The user ID and password are only required if the proxy used requires a user ID and password. If not, the proxy parameter would look like this: PROXY(XXXXXX *IBMSVR *TRYAFTER)
2. *TRYAFTER is the default; however, if the user wants to have the proxy attempted first, they need to specify *TRYBEFORE.
- Profiles QVPN01IBM1 and QVPN01IBM2 are created for 7.5 and older.
3. If the user ID or password for the proxy is case-sensitive, include single quotation marks around the values, for example 'uUUuu' ('PpppP')
Creating a Multihop HTTP/HTTPS Connection for the Local System
To set up a multi-hop environment that uses HTTP/HTTPS, one system can be set up as an HTTP/HTTPS proxy HUB and then other systems can use this system as the proxy server.
To create the primary HUB system, which connects to IBM using HTTP/HTTPS:
CRTSRVCFG ROLE(*PRIMARY) CNNTYPE(*DIRECT) CNNPNT(*YES ((*ALL)))
The other systems will be configured to use the HUB system as a proxy server:
CRTSRVCFG ROLE(*PRIMARY) CNNTYPE(*DIRECT) CNTRYID(*SELECT) STATE(*SELECT) CNNPNT(*NO) PROXY(HUB_System_Name *IBMSVR *TRYBEFORE)
*IBMSVR use port 5026 which must be open for both systems to be able to communicate.
Was this topic helpful?
Document Information
Modified date:
02 June 2026
UID
nas8N1018762