CUSTOM parameter

Enable special modifications to Model 204

Summary

Default value

None

Parameter type

System

Where set

On User 0's parameter line or reset by the system manager

Related products

All

Introduced

Model 204 V6.1 or earlier

Description

The CUSTOM parameter enables special modifications by Rocket Software to standard execution.

You do not have to enclose a single CUSTOM setting with parentheses, for example:

CUSTOM=8

Multiple values must be specified in a list and enclosed in parentheses, for example:

CUSTOM=(1,2,3,4,6,8,9,10,11)

The current values and their meanings are:

Setting	Usage	Introduced
1	Century can be omitted on date input.	V4.1
2	Century is omitted on date output.	V4.1
3	$DAYI should return day values 2 through 8 (instead of 1 through 7). $DAY should equate values 2 through 8 as Monday through Sunday, and full-length day names should be returned. Value 9 returns MON-FRI.	V4.1
4	DISPLAY FIELD fieldname Defaults to: DISPLAY FIELD (DDL ABBREV) fieldname	V4.1
5	Print debugging information for all MQ/204 requests.	V4.2
6	The LOGOUT message is: M204.2628: uuuuuuuuuu aaaaaaaaaa LOGOUT yy mmm dd hh.mm	V5.1
7	Obsolete as of Model 204 V7.1.	V5.1
8	Connect★ clients can issue the LOGIN command from Remote Command Line (RCL) threads. Clients can login with a new user name without closing the current connection to start another one.	V6.1
9	Suppresses all output from all forms of the PRIORITY command.	V7.1
10	Allows file name entry using more than eight characters.	V7.4
11	Controls mixed-case password support for login passwords. If it is set, mixed-case login passwords are allowed for both external and CCASTAT security. If it is not set, all login passwords are uppercase.	V7.4
12	Swap order of system manager and system administrator test with external authorizer. Only available in Model 204 V7.5 and later.	V7.5
13	Close VSAM files even if CLOSE=EOJ specified.	V7.5
14	Require account ID (in addition to userid) on logins.	V7.5
15	Don't display user number on console (WTO) messages.	V7.5
16	Append the userid of the updating user to the date-time stamp (DTSFN) field values.	V7.5
17	Preserves plus sign (+) in ASA column 1 for VBA datasets and USE PRINTER output to allow for overtyping. Line must contain plus sign in column 1, followed by blank, followed by anything: PRINT '+ anything'	V7.5
18	Allow SSLIBSIZE (JANUS DEFINE parameter) value greater than 16K (16384).	V7.5
19	Change the Login failed message from: M204.0349: Login failed To: M204.0349: Enter logoff	V7.5; zap 75Z279 required
20	Suppress the last line in the LOGCTL dialog during ADD, CHANGE, and DELETE. LOGCTL C USER1 *** M204.0374: ENTER PASSWORD,PRIVILEGES,PRIORITY *** M204.0379: Enter terminal list, all, none, add, del, or return USER1 X'10' LOW ALL <--------suppress this line *** M204.0376: Parameters accepted *** M204.0345: CCASTAT updated	V7.5; zap 75Z279 required
21	FILELOAD; skip DDname check for CCA1WK01 to allow DFSORT to dynamically allocate sort work datasets. DFSORT will dynamically allocate CCA1WK01-CCA1WK06 unless overridden by //DFSPARM: //DFSPARM DD * // SIZE=200M,LIST,LISTX,MSGPRT=ALL,FILSZ=E1800000 // OPTION DYNALLOC=(SYSDA,3) <------will override	V7.5; zap 75Z279 required
22	Use BATCH204 return codes if NUSERS is greater than 1.	V7.5; zap 75Z279 required
31	Extra bug checks for Ordered Index leaf pages.	V7.5
32	Extra bug checks for all Ordered Index pages.	V7.5
33	Issue a message (M204.1223) for every critical file resource wait.	V7.5
34	Suppress APSY load stats from the journal.	V7.5
35	Do not drain a subsystem when a user encounters a hard restart inside the subsystem.	V7.5
36	An Insert statement with occurrence number 0 should place the inserted occurrence at the start of repeatable fields in the record.	V7.5
37	Change M204.1076 (Do you really want to end the run) to indicate the job name rather than the location.	V7.5
38	Allow any (non-privileged) user to reset LAUDIT.	V7.5
39	Echo any MSGCTL command in a M204.0131 message.	V7.5
40	Allow field constraints (UNIQUE, At-MOST-ONE) in non-TBO (FRCVOPT X'08' bit on) files.	V7.5

Using the CUSTOM=(1) parameter with date conversions

If CUSTOM=(1) is added to the User 0 CCAIN stream or set later using the RESET command, the following occurs: If a CYY format is specified for conversion and only a YY input is supplied, the conversion is successfully completed by using the CENTSPLT and BASECENT parameters.

Examples

If CUSTOM=1, BASECENT=19, and CENTSPLT=95, then:

Print command	Results
PRINT $DATECNV('CYYDDD','YYYYMMDD','96001'	19960101
PRINT $DATECNV('CYYDDD','YYYYMMDD','196001'	20960101
PRINT $DATECNV('CYYDDD','YYYYMMDD','95001'	19950101
PRINT $DATECNV('CYYDDD','YYYYMMDD','095001'	19950101

If CUSTOM=1 is omitted, BASECENT=19, and CENTSPLT=95, then:

Print command	Results
PRINT $DATECNV('CYYDDD','YYYYMMDD','96001'	******
PRINT $DATECNV('CYYDDD','YYYYMMDD','196001'	20960101
PRINT $DATECNV('CYYDDD','YYYYMMDD','95001'	******
PRINT $DATECNV('CYYDDD','YYYYMMDD','095001'	19950101

Using CUSTOM=(2)

If CUSTOM=(2) is added to the User 0 CCAIN stream or set later using the RESET command, the following occurs: If a CYY-format is specified for output conversion and the C (century) indicator is zero, then C is eliminated. This C elimination is true for all $DATE… function calls.

For example:

If CUSTOM=(2) then: PRINT $DATEJ(2) prints 97.001

But if CUSTOM=(2) is omitted, then PRINT $DATEJ(2) prints 097.001.

Using CUSTOM=(6)

Using this option you can control the messages for the LOGIN and LOGOUT commands independently.

• When CUSTOM is not set to 6, BATCH2 and IFAM2 applications cannot receive the return code from Model 204, if the command MSGCTL M204.0353 NOTERM is issued in the Online. Model 204 sends the return code to BATCH2 and IFAM2 User Language applications as a hidden field in the LOGOUT message, and the application must receive the LOGOUT message to obtain the return code.
• When CUSTOM is set to 6, you can suppress M204.0353 and leave M204.2628 active and available for a BATCH2 or IFAM2 User Language application to receive the return code from the Online.

Using CUSTOM=(8)

The CUSTOM=(8) option lets Connect★ customers use one connection for multiple users.

• If CUSTOM=(8) is not set, RCL behaves as in releases of Model 204 before V6R1.0; users receive the following message when issuing the LOGIN command:

  M204.1035:COMMAND INVALID FROM PROCEDURE

• If CUSTOM=(8) is set, any commands that are invalid for RCL receive the following message:

  M204.2597 command COMMAND INVALID FROM AN RCL THREAD

Using CUSTOM=(9)

The CUSTOM=(9) option lets you suppress all output from all forms of the PRIORITY command.

Using CUSTOM=(10)

Including CUSTOM=10 in the CCAIN parameter stream enables you to specify a DDNAME longer than eight characters. The first eight characters will be used.

Using CUSTOM=(11)

Including CUSTOM=11 in the CCAIN parameter stream enables you to specify login passwords containing lowercase characters:

//CCAIN DD * LOGADD=200,CUSTOM=11

Using CUSTOM=(12)

When using an external authorizer (RACF, ACF2, Top Secret), if a user issues a command that requires system manager or system administrator privileges, Model 204 will test for system manager privileges for the logged-in user using the external authorizer and, if that fails, test for system administrator privileges. CUSTOM=(12) changes the order of the tests in such a case so that a user is tested for system administrator privileges before being tested for system manager privileges.

Using CUSTOM=(18)

Before Model 204 7.5, a setting of greater than 16K (16384) was allowed for the SSLIBSIZE parameter of the JANUS DEFINE command. However, in theory this should have only been necessary for SSL 2 support, as SSL 3 and TLS compliant implementations should only use SSL records of 16K or shorter. Since support for SSL 2 has been disabled in Model 204 7.5 (because SSL 2 is deprecated for its many security flaws), there is seemingly no need for SSL buffers longer than the 16K limit. So, Model 204 7.5 reduces any value greater than 16K for SSLBSIZE and SSLOBSIZE to 16K. This prevents Model 204 from pointlessly allocating more storage than is necessary for SSL buffers.

However, it appears that there are a few SSL 3 and TLS implementations in use that send SSL records longer than 16K, despite the standard's proscription against doing so. If a site communicates with such implementations, it might be necessary to set CUSTOM 18, then set SSLIBSIZE (or SSLOBSIZE) to a value greater than 16K.