Skip to main content
Version: v3.1.x LTS

Editing team configurations

Editing team configurations

After you initialize team configuration, the newly created team profiles need additional details before they can be shared and applied in your environment. This could include information such as a port number or user credentials.

You might also need to modify the configuration file to create new profiles for accessing mainframe services.

Adding, modifying team profiles

To define additional mainframe services and other profiles in an existing global team configuration file:

  1. Open the ~/.zowe/zowe.config.json file in a text editor or an IDE (such as Visual Studio Code) on your computer.

  2. Edit the file by adding to or modifying the profiles listed in the profiles object.

    Each profile contains connection and other frequently needed information for accessing various mainframe services, as in the following example:

    {
    "$schema": "./zowe.schema.json",
    "profiles": {
    "zosmf": {
    "type": "zosmf",
    "properties": {
    "port": 443
    }
    },
    "global_base": {
    "type": "base",
    "properties": {
    "host": "example1.com"
    },
    "secure": [
    "user",
    "password"
    ]
    }
    },
    "defaults": {
    "zosmf": "zosmf",
    "base": "global_base"
    },
    }

Available service profile types

A profile contains all, or most, of the information you need to connect to a specific mainframe service. Your configuration can have multiple profiles, and these can consist of different profile types and even different kinds of a particular profile type, depending on the connection information.

There are three basic profile types:

  • service profiles
  • base profiles
  • parent profiles

You can learn more about how service, base, and parent profiles work in Zowe CLI profile types.

Core z/OS service profiles

The three z/OS services that Zowe CLI and Zowe Explorer profiles connect to:

  • z/OSMF profiles connect with the IBM z/OS Management Facility service.
  • TSO profiles connect with the Time Sharing Option service.
  • SSH profiles connect with the Secure Shell service.

Zowe CLI plug-in service profiles

Other kinds of service profiles can be used to configure connections for Zowe CLI plug-ins. A base profile, on the other hand, contains connection data that can be shared across multiple service profiles.

To determine the types of plug-in service profiles that can be used in Zowe CLI configuration, refer to the tables on this page or check the Zowe CLI plug-in command groups listed in the Zowe web help. Most group names match the plug-in profile name.

Profile properties

Every profile in a configuration file includes specific information, such as properties and their values, to communicate with its respective mainframe service. The values for properties are defined by your specific connection information.

The available properties for z/OS services and Zowe-conformant plug-ins profiles are listed in the following tables:

base

PropertyDescriptionAllowed
hostHost name of service on the mainframe.string
portPort number of service on the mainframe.number
userUser name to authenticate to service on the mainframe.string
passwordPassword to authenticate to service on the mainframe.string
rejectUnauthorizedReject self-signed certificates.

Default: true
boolean:
true
false
tokenTypeThe type of token to get and use for the API. Omit this option to use the default token type, which is provided by zowe auth login.string
tokenValueThe value of the token to pass to the API.string
certFileThe file path to a certificate file to use for authentication.

Note:
The CLI does not support certificate files that require a password. For more information, see PEM certificate files.
string
certKeyFileThe file path to a certificate key file to use for authenticationstring

ca7

PropertyDescriptionAllowed
hostHost name of the CA7 API service that is running on the mainframe system.string
portPort for the CA7 API service that is running on the mainframe system.number
userUser name for authenticating connections to the CA7 API service that is running on the mainframe system.string
passwordPassword for authenticating connections to the CA7 API service that is running on the mainframe system.string
basePathThe base path for your API Mediation Layer instance. Specify this option to prepend the base path to all resources when making REST requests. Do not specify this option if you are not using an API Mediation Layer.string
protocolSpecifies protocol to use for CA7 connection.string:
http
https
rejectUnauthorizedReject self-signed certificates.

Default: true
boolean:
true
false

cics

PropertyDescriptionAllowed
hostThe CMCI server host namestring
portThe CMCI server port

Default: 1490
number
userYour username to connect to CICSstring
passwordYour password to connect to CICSstring
regionNameThe name of the CICS region name to interact withstring
cicsPlexThe name of the CICSPlex to interact withstring
rejectUnauthorizedReject self-signed certificates.

Default: true
boolean:
true
false
protocolSpecifies CMCI protocol.

Default: https
string:
http
https

db2

PropertyDescriptionAllowed
hostThe Db2 server host namestring
portThe Db2 server port numbernumber
userThe Db2 user ID (may be the same as the TSO login)string
passwordThe Db2 password (may be the same as the TSO password)string
databaseThe name of the databasestring
sslFilePath to the root CA Certificate filestring

dbm-db2

PropertyDescriptionAllowed
hostSpecifies the DBM Data Service REST API server host name or TCP/IP address to use.string
portSpecifies the DBM Data Service REST API server TCP/IP port number.

Default: 7300
number
userSpecifies the mainframe user name that you want to use to connect to the mainframe systems during execution of the Zowe CLI commands. This user name can be the same as your TSO login ID.string
passwordSpecifies the mainframe password for the user name that is used to connect to the mainframe systems during execution of the CLI commands. This password can be the same as your TSO password.string
protocolSpecifies the communication protocol between zowe dbm-db2 client and DBM Data Service.

Default: https
string:
http
https
rejectUnauthorizedDetermines whether the dbm-db2 command is accepted or rejected when a self-signed certificate is returned by the DBM Data Service.

Default: true
boolean:
true
false
environmentListSpecifies a string of one or more entries consisting of a Db2 subsystem ID and a DBM Data Service REST API server host name or TCP/IP address. Use a comma to separate entries. The same Db2 subsystem can be used in multiple DBM Data Service environments. For more information about configuring the DBM Data Service, see the Database Management Solutions for Db2 for z/OS documentation.

Default:
{
    "ssid1": "env1@host1:port1",
    "ssid2": "env2@host2:port2"
}
object
jobCardsSpecifies a string array of z/OS JCL JOB statements.

Default:
//DB2DVOPS JOB CLASS=A,
//     MSGCLASS=X
array
workDatasetPrefixSpecifies the prefix (high-level qualifier) in z/OS work data set names.

Default: ${user}.dbmdb2
string
deleteWorkDatasetsSpecifies whether to delete work data sets on a mainframe after the request is fulfilled.

Default: true
boolean:
true
false
overwriteOutputFilesSpecifies whether to overwrite output files if they exist.

Default: false
boolean:
true
false
authidSpecifies the primary Db2 authorization ID that is used to establish a connection between Db2 and a process.

Default: ${user}
string
sqlidSpecifies the authorization ID that is used in generated SET CURRENT SQLID statements.

Default: ${user}
string
terminationCharacterSpecifies the SQL termination character to use in DDL generation when the default termination character conflicts with the SQL statements that are used in triggers, XML indexes, and routines (external SQL functions and native SQL stored procedures). The default termination character is a semi-colon (;). You cannot specify a comma, double quote, single quote, left or right parentheses, or an underscore.

Default: ;
string
basePathThe base path for your API Mediation Layer instance. Specify this option to prepend the base path to all DBM DS resources when making REST requests. Do not specify this option if you are not using an API Mediation Layer.string

dbm-db2-options

PropertyDescriptionAllowed
authidSpecifies the primary Db2 authorization ID that is used to establish a connection between Db2 and a process.string
changeSetSpecifies the creator and name of an existing RC/Migrator global change set that changes Db2 objects during a command execution.

Format:
<change-set-creator.change-set-name>

For more information about global change services, see the RC/Migrator documentation.

Note:
If change-set and change-set-file are both specified, specifications in change-set-file take precedence.
string
changeSetValuesSpecifies the global change specifications that modify Db2 object attributes during a command execution.

Format:
<object-attribute> <from-value> <to-value>
  
The <object-attribute> consists of four characters. The first two characters identify the object type. The last two characters identify the specific attribute. Wildcard characters are supported in <from-value> and <to-value>. If the same <object-attribute> is specified multiple times, the first occurrence takes precedence.
 
For a full list of attributes, see Global Change Set Attributes in the RC/Migrator documentation.

Example:
The following example demonstrates changes to the table schema (creator) and tablespace names:
  
TBCR TEST% PROD%
TBTS TESTTS% PRODTS%

Note:
- If change-set and change-set-file are both specified, specifications in change-set-file take precedence.
- The changeSetValues options-profile option has the same behavior as the change-set-file command option.

Default:
-- DDL changes for a table with dependent objects.
-- Note: Replace CHANGEME with your database name.
ALDB * CHANGEME
ALCR * ${user}
TBTC * ${user}
IXTC * ${user}
VWTC * ${user}
VWFS * ${user}
SYTC * ${user}
ASTC * ${user}
TGSC * ${user}
TGOW * ${user}
TGTC * ${user}
TGTO * ${user}
TGQU * ${user}
TGFS * ${user}
TGQS * ${user}
SQSC * ${user}
RTSC * ${user}
RTPO * ${user}
RTQU * ${user}
array
deleteWorkDatasetsSpecifies whether to delete work data sets on a mainframe after the request is fulfilled.boolean:
true
false
descriptionSpecifies a 1- to 25-character description for the RC/Migrator compare strategy.string
idSpecifies the 1- to 8-character name of the RC/Migrator compare strategy that is created on the target Db2 subsystem during a command execution.

Format:
The name must begin with a non-numeric character and contain the following characters only: uppercase letters from A to Z, numbers from 0 to 9, and special characters $, #, and @.
string
jobCardsSpecifies a string array of z/OS JCL JOB statements.array
matchSetSpecifies the creator and name of an existing RC/Migrator automapping mask set. Matching is used to pair objects in a DDL file to objects that are defined on a Db2 subsystem. Matching determines whether the change-set or rule-set options are applied.

Format:
<match-set-creator.match-set-name>

For more information about mask services, see the RC/Migrator documentation.

Note:
If --match-set and --match-set-file are both specified, specifications in match-set-file take precedence.
string
matchSetValuesSpecifies the mapping mask specifications. Matching is used to pair objects in a DDL file to objects that are defined on a Db2 subsystem. For example, a mask specification can account for different schema naming patterns across environments. Matching determines whether the change-set or rule-set options are applied.

Format:
<object-type> <source-name-mask> <target-name-mask>;

STOGROUP <name> <name>
DATABASE <name> <name>
TABLESPACE <database.name> <database.name>
TABLE <schema.name> <schema.name>
INDEX <schema.name> <schema.name>
VIEW <schema.name> <schema.name>
SYNONYM <schema.name> <schema.name>
ALIAS <schema.name> <schema.name>
TRIGGER <schema.name> <schema.name>
SEQUENCE <schema.name> <schema.name>
FUNCTION <schema.name[.version]> <schema.name[.version]>
PROCEDURE <schema.name[.version]> <schema.name[.version]>

Note:
- <name> must be between 1 and 128 characters. For DATABASE and TABLESPACE, <name> must be between 1 and 8 characters.
- <schema> must be between 1 and 128 characters.
- <version> must be between 1 and 64 characters.
          
A mask specification can include the following wildcard characters:
          
Percent sign (%) indicates that zero or more characters can occupy that position and all remaining positions to the end of the name, or to the next character. The percent sign can be used anywhere in the name. However, the source and target characters must match exactly.

Hyphen or dash (-) indicates that any character can occupy that position, but a character must exist at that position, and the source and target character must match exactly. The hyphen can be repeated in several places in the name.

Asterisk (*) indicates matching values. An asterisk cannot be used with other characters.
          
Use a semicolon to separate mask specifications. Multiple mask specifications for the same object type are supported.

Example:
The following example demonstrates different ways of matching the table MYNAME.MYTABLE to the table YOURNAME.YOURTABLE:

TABLE MY%.%TABLE YOUR%.%TABLE;
TABLE MYN-M-.MYT% YOURN-M-.YOURT%;
TABLE MYNAME.MYTABLE YOURNAME.YOURTABLE;
TABLE *.MYTABLE *.YOURTABLE;

For a list of mask specifications, see the RC/Migrator documentation.

Note:
- If --match-set and --match-set-file are both specified, specifications in match-set-file take precedence.
- The matchSetValues options-profile option has the same behavior as the match-set-file command option.
array
modificationSpecifies a named set of server-managed default parameter values that control the execution behavior of the zowe dbm-db2 commands. For example, you can use a modification to identify a set of default values that differ from the current set of default values.
 
For more information about using the modification option, see the DBM Data Service documentation.
string
overwriteOutputFilesSpecifies whether to overwrite output files if they exist.boolean:
true
false
ruleSetSpecifies the creator and name of an existing RC/Migrator rule set that overrides Db2 object attributes in the target Db2 subsystem with the corresponding values from the input DDL file. The changes only apply to existing objects, as determined by match-set processing.

Format:
<rule-set-creator.rule-set-name>
    
For more information about rule database services, see the RC/Migrator documentation.
string
sqlidSpecifies the authorization ID that is used in generated SET CURRENT SQLID statements.string
sourceDb2Specifies the source Db2 subsystem or data sharing group where the objects that you want to use in a command are located.

Note:
If you specify the data sharing group, the first active Db2 subsystem in the group is used.
string
targetDb2Specifies the target Db2 subsystem or data sharing group where you want to use a command.

Note:
If you specify the data sharing group, the first active Db2 subsystem in the group is used.
string
terminationCharacterSpecifies the SQL termination character to use in DDL generation when the default termination character conflicts with the SQL statements that are used in triggers, XML indexes, and routines (external SQL functions and native SQL stored procedures). The default termination character is a semi-colon (;). You cannot specify a comma, double quote, single quote, left or right parentheses, or an underscore.string
typeSpecifies the type of DDL statements that you want to generate. You can generate CREATE or DROP statements.string:
drop
create
verifySpecifies whether to verify that the objects to be created do not exist on the Db2 subsystem and that the related objects that are required for successful creation of the objects exist on the Db2 subsystem or in the input DDL.

Default: no
string:
yes
no
workDatasetPrefixSpecifies the prefix (high-level qualifier) in z/OS work data set names.string

endevor

PropertyDescriptionAllowed
hostThe hostname of the endevor sessionstring
portThe port number of the endevor sessionnumber
userThe username of the endevor sessionstring
passwordThe password of the userstring
protocolThe protocol used for connecting to Endevor Rest API

Default: https
string:
http
https
basePathThe base path used for connecting to Endevor Rest API

Default: EndevorService/api/v2
string
rejectUnauthorizedIf set, the server certificate is verified against the list of supplied CAsboolean:
true
false
reportDirThe default path where any reports will be written to, either absolute or relative to current directory

Default: .
string

endevor-location

PropertyDescriptionAllowed
instanceThe STC/datasource of the session

Default: ENDEVOR
string
environmentThe Endevor environment where your project resides

Default: DEV
string
systemThe Endevor system where the element residesstring
subsystemThe Endevor subsystem where your element residesstring
typeName of the Endevor element's typestring
stageNumberThe Endevor stage where your project residesstring:
1
2
commentThe Endevor comment you want to use when performing an actionstring
ccidThe Endevor CCID you want to use when performing an actionstring
maxrcThe return code of Endevor that defines a failed action

Default: 8
number
override-signoutAlways override element signout, without having to specify the override signout option on each command

Default: false
boolean:
true
false
file-extensionThe strategy for deciding what file extension to use during a bulk retrieve or workspace synchronization. Must be one of the following:

none:
File name is equal to element name, no extension is added.

file-ext:
The file extension defined in the Type definition is used; If not defined, no extension is added.

type-name:
The type name is used as the file extension.

mixed:
The file extension defined in Type definition is used; If not defined, the type name is used instead.

Default: mixed
string:
none
type-name
file-ext
mixed

ims

PropertyDescriptionAllowed
hostThe IMS Operations API server host name.string
portThe IMS Operations API server port.number
imsConnectHostThe hostname of your instance of IMS Connect. This is typically the hostname of the mainframe LPAR where IMS Connect is running.string
imsConnectPortThe port of your instance of IMS Connect. This port can be found in your IMS Connect configuration file on the mainframe.number
plexThe name of the IMS plex.string
userThe web server user name where the IMS Operations API resides.string
passwordThe web server user password where the IMS Operations API resides.string
basePathThe base path for your API Mediation Layer instance. Specify this option to prepend the base path to all z/OSMF resources when making REST requests. Do not specify this option if you are not using an API Mediation Layer.string
protocolSpecifies protocol.

Default: https
string:
http
https
rejectUnauthorizedReject self-signed certificates.

Default: true
boolean:
true
false

jclcheck

PropertyDescriptionAllowed
hostHost name of the JCLCheck API service that is running on the mainframe system.string
portPort for the JCLCheck API service that is running on the mainframe system.

Default: 12697
number
userUser name for authenticating connections to the JCLCheck API service that is running on the mainframe system.string
passwordPassword for authenticating connections to the JCLCheck API service that is running on the mainframe system.string
basePathThe base path for your API Mediation Layer instance. Specify this option to prepend the base path to all resources when making REST requests. Do not specify this option if you are not using an API Mediation Layer.

Default: cajclcheck/api/v1
string
rejectUnauthorizedReject self-signed certificates.

Default: true
boolean:
true
false
protocolSpecifies protocol to use for JCLCheck connection.

Default: https
string:
http
https
jclcheckOptionsThe desired set of JCLCheck runtime options. Specify the options exactly as you would on the PARM= or OPTIONS DD on a batch run of JCLCheck. See the JCLCheck runtime options documentation for details on available runtime options. If you specify options that change the format of the JCLCheck reports, you should request --raw-output. Changing the format of the report will affect the ability to produce a structured API response.string

mat

PropertyDescriptionAllowed
protocolSpecifies the protocol defined for the MAT REST API server.

Default: https
string:
http
https
hostnameSpecifies the hostname or IP address defined for the MAT REST API server (e.g. 127.0.0.0 or localhost).string
portSpecifies the server port (e.g. 8080).number
userYour mainframe username.string
passwordYour mainframe password.string
basePathThe base path for your API Mediation Layer instance. Specify this option to prepend the base path to all resources when making REST requests. Do not specify this option if you are not using an API Mediation Layer.string
rejectUnauthorizedReject self-signed certificates.

Default: true
boolean:
true
false
listingDirSpecifies the directory where you want to store the registered program listings (e.g. c:\listings) for your immediate source code inspection. You can use the advantage of automated listing registration with MAT and listing retrieval through Endevor® footprints for Cobol, C/C++, and Assembler programs. When a source program listing is registered with MAT, you can enhance the histogram analysis data with the program listing details that pertain to the specific CSECT and program statement. The listing is transfered to the specified directory, which enables you to navigate directly to the line of the source code in you VS Code IDE and inspect the program statement. To use the listing retrieval option through Endevor® footprints, you need to have the Endevor® Web Services installed and configured and specify the Endevor® web server details in the MAT database configuration.string

mq

PropertyDescriptionAllowed
hostThe host name used to access the IBM MQ REST API. This might be the host name of the IBM MQ mqweb server, or the Zowe API Mediation Layer..string
portThe port number used to access the IBM MQ REST API. This might be the port number of the IBM MQ mqweb server, or the Zowe API Mediation Layer.number
userThe mainframe (MQ) user name, which can be the same as your TSO login.string
passwordThe mainframe (MQ) password, which can be the same as your TSO password.string
rejectUnauthorizedReject self-signed certificates.

Default: false
boolean:
true
false
protocolSpecifies the MQ protocol.

Default: https
string:
http
https

omspool

PropertyDescriptionAllowed
accountz/OS TSO/E accounting information.string
spoolhlqHigh level qualifier of OM Spool installation.string
subsysOM Spool subsystem name.

Default: ESF
string
outdsThe SYSTSPRT data set allocated by CAI.CBQ4JCL(BQ4JZOWE). It must be unique for each Zowe CLI user interacting with OM Spool.string
clistThe data set containing ESFZOWE REXX exec.string

omview

PropertyDescriptionAllowed
protocolProtocol of the target OM Web Viewer instance.

Default: https
string:
http
https
hostHostname or ip address of the target OM Web Viewer instance.string
portPort of the target OM Web Viewer instance.

Default: 443
number
basePathContext name of the target OM Web Viewer instance.

Default: web-viewer
string
userUser name used to authenticate against the target OM Web Viewer instance.string
passwordPassword used to authenticate against the target OM Web Viewer instance.string

ops

PropertyDescriptionAllowed
hostThe hostname of the server where OPS/MVS Web Services / REST API is running.string
portThe port number for OPS/MVS Web Services / REST API.number
userYour z/OS user name that is used to authenticate to OPS/MVS Web Services / REST API.string
passwordYour z/OS password that is used to authenticate to OPS/MVS Web Services / REST API.string
protocolThe protocol that is used for connecting to OPS/MVS Web Services / REST API.

Default: https
string:
http
https
rejectUnauthorizedIf set to true, the server certificate is verified against the list of supplied CAs. If set to false, certificate verification is not performed.

Default: true
boolean:
true
false
subsystemSpecifies the subsystem ID of the OPS/MVS instance to which commands will be directed. This parameter is ignored by the show status and show subsystem commands.

Default: OPSS
string
restApiIf set to true, the plug-in executes the command against the OPS/MVS REST API. If set to false, the plug-in executes against the OPS/MVS Web Services.

Default: false
boolean:
true
false
basePathIf set to true, the plug-in executes the command against the OPS/MVS REST API. If set to false, the plug-in executes against the OPS/MVS Web Services.

Default: false
string

pma

PropertyDescriptionAllowed
job_acctSpecifies z/OS TSO/E accounting information. Values: numeric characters (0-9)string
job_classYour z/OS class information. Values: alphanumeric characters (A-Z, 0-9)string
job_mclassSpecifies the MSGCLASS parameter value and assigns the job log to the specified output class. The specified MSGCLASS value is used in all JCLs that PMA runs while you execute the commands. If you do not provide the job_mclass parameter, the default MSGCLASS value is used. Values: alphanumeric characters (A-Z, 0-9)

Default: A
string
job_loadSpecifies the PMA loadlib data set name that you defined during the PMA customization (&HLQ.CEETLOAD)string
job_pmahlqSpecifies your PMA HLQ to access the KSDSALT, KSDSJOB, and KSDSEXC VSAM files that ensure the collection of the necessary datastring

rse

PropertyDescriptionAllowed
hostThe z/OS host name running the Zowe REST API.string
portThe server port used by the REST API.

Default: 6800
number
userThe user name for the Zowe REST API operations.string
passwordThe password of the user for the Zowe REST API operations.string
rejectUnauthorizedReject self-signed certificates.

Default: true
boolean:
true
false
basePathThe base path of the API for the REST API operations.

Default: rseapi
string
protocolOnly HTTPS supported for a TLS handshake to access REST API.

Default: https
string:
https
encodingThe encoding for download and upload of z/OS data set and USS files. The encoding should be specified in the form of "IBM-1047".string
tokenTypeJWT type assigned to profile when "zowe rse auth login" is used for authentication.string
tokenValueJWT value assigned to profile when "zowe rse auth login" is used for authentication.string
tokenExpirationJWT expiration assigned to profile when "zowe rse auth login" is used for authentication.string

ssh

PropertyDescriptionAllowed
hostThe z/OS SSH server host name.string
portThe z/OS SSH server port.

Default: 22
number
userMainframe user name, which can be the same as your TSO login.string
passwordMainframe password, which can be the same as your TSO password.string
privateKeyPath to a file containing your private key, that must match a public key stored in the server for authenticationstring
keyPassphrasePrivate key passphrase, which unlocks the private key.string
handshakeTimeoutHow long in milliseconds to wait for the SSH handshake to complete.number

sysview

PropertyDescriptionAllowed
hostThe hostname of the SYSVIEW REST APIstring
portThe port number of the SYSVIEW REST APInumber
userYour z/OS username used to authenticate to the SYSVIEW REST APIstring
passwordYour z/OS password used to authenticate to the SYSVIEW REST APIstring
rejectUnauthorizedIf set, the server certificate is verified against the list of supplied CAsboolean:
true
false
ssidSSID of the SYSVIEW instance.

Default: GSVX
string
basePathThe base path for your API Mediation Layer instance. Do not specify this option if you are not using an API Mediation Layer.

Default: /api/v1
string

sysview-format

PropertyDescriptionAllowed
contextFieldsContext fields to display. Defaults to hiding all contextarray
overviewDisplay the overview sectionboolean:
true
false
infoDisplay the information area, if anyboolean:
true
false
prettyDisplay formatted databoolean:
true
false
blankIfZeroShow a blank space instead of 0 valuesboolean:
true
false
truncateTruncate displays that are too wide for the console

Default: false
boolean:
true
false

tso

PropertyDescriptionAllowed
accountYour z/OS TSO/E accounting information.string
characterSetCharacter set for address space to convert messages and responses from UTF-8 to EBCDIC.

Default: 697
string
codePageCodepage value for TSO/E address space to convert messages and responses from UTF-8 to EBCDIC.

Default: 1047
string
columnsThe number of columns on a screen.

Default: 80
number
logonProcedureThe logon procedure to use when creating TSO procedures on your behalf.

Default: IZUFPROC
string
regionSizeRegion size for the TSO/E address space.

Default: 4096
number
rowsThe number of rows on a screen.

Default: 24
number

zftp

PropertyDescriptionAllowed
hostThe hostname or IP address of the z/OS server to connect to.string
portThe port of the z/OS FTP server.

Default: 21
number
userUsername for authentication on z/OSstring
passwordPassword to authenticate to FTP.string
secureFtpSet to true for both control and data connection encryption, control for control connection encryption only, or implicit for implicitly encrypted control connection (this mode is deprecated in modern times, but usually uses port 990).

Note: Unfortunately, this plug-in's functionality only works with FTP and FTPS, not SFTP which is FTP over SSH.

Default: true
boolean,null
rejectUnauthorizedReject self-signed certificates. Only specify this if you are connecting to a secure FTP instance.boolean,null
servernameServer name for the SNI (Server Name Indication) TLS extension. Only specify if you are connecting securelystring,null
connectionTimeoutHow long (in milliseconds) to wait for the control connection to be established.

Default: 10000
number
encodingThe encoding for download and upload of z/OS data set.string

zosmf

PropertyDescriptionAllowed
hostThe z/OSMF server host name.string
portThe z/OSMF server port.

Default: 443
number
userMainframe (z/OSMF) user name, which can be the same as your TSO login.string
passwordMainframe (z/OSMF) password, which can be the same as your TSO password.string
rejectUnauthorizedReject self-signed certificates.

Default: true
boolean:
true
false
certFileThe file path to a certificate file to use for authenticationstring
certKeyFileThe file path to a certificate key file to use for authenticationstring
basePathThe base path for your API Mediation Layer instance. Specify this option to prepend the base path to all z/OSMF resources when making REST requests. Do not specify this option if you are not using an API Mediation Layer.string
protocolThe protocol used

Default: https
string:
http
https
encodingThe encoding for download and upload of z/OS data set and USS files. The default encoding if not specified is IBM-1047.string
responseTimeoutThe maximum amount of time in seconds the z/OSMF Files TSO servlet should run before returning a response. Any request exceeding this amount of time will be terminated and return an error. Allowed values: 5 - 600number