CUSTOM parameter

From m204wiki
Revision as of 13:18, 27 December 2013 by Alex (talk | contribs) (→‎Description)
Jump to navigation Jump to search

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 usages are:

SettingUsage
CUSTOM=(1)Century can be omitted on date input
CUSTOM=(2)Century is omitted on date output
CUSTOM=(3)$DAYI should return day values 2 through 8. $DAY should equate value 2 through 8 as Monday through Sunday and full length day name should be returned. Value 9 returns MON-FRI.
CUSTOM=(4)Display field defaults to DDL ABBREV
CUSTOM=(5)Print debugging information for all MQ/204 requests.
CUSTOM=(6)The LOGOUT message is:

M204.2628: uuuuuuuuuu aaaaaaaaaa LOGOUT yy mmm dd hh.mm

CUSTOM=(7)Obsolete as of Model 204 V7R1.0.
CUSTOM=(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.
CUSTOM=(9)Suppresses all output from all forms of the PRIORITY command
CUSTOM=(10)Allows filename entry using more than eight characters
CUSTOM=(11)Controls mixed case password support. If it is set, then mixed case passwords are allowed for both external and CCASTAT security. If it is not set, all passwords are uppercase.
CUSTOM=(12)Swap order of system manager and system administrator test with external authorizer. Only available in Model 24 7.5 and later.
CUSTOM=(31)Extra bug checks for ordered index leaf pages.
CUSTOM=(32)Extra bug checks for all ordered index pages.
CUSTOM=(33)Issue a message (M204.1223) for every critical file resource wait.
CUSTOM=(34)Suppress APSY load stats from the journal.
CUSTOM=(35)Do not drain a subsystem when a user encounters a hard restart inside the subsystem.
CUSTOM=(36)An Insert statement with occurrence number 0 should place the inserted occurrence at the start of repeatable fields in the record.
CUSTOM=(37)Change M204.1076 (Do you really want to end the run) to indicate the job name rather than the location.
CUSTOM=(38)Allow any (non-privileged) user to reset LAUDIT.
CUSTOM=(39)Echo any MSGCTL command in a M204.0131 message.
CUSTOM=(40)Allow field constraints (UNIQUE, At-MOST-ONE) in non-TBO (FRCVOPT X'08' on) files.

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.

See "CENTSPLT: Computing the base century" and "BASECENT: Base century value" for details.

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 six, 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 the 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 the 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 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 either system manager or system administrator privileges, Model 204 will test for system manager privileges for the logged in user using the extrenal 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.