Standard MVS linkage is provided for the exit program call.
R13
points to an 18 word save area
R14
contains the return address
R15
contains the entry point of B97UXSEC
On entry to the exit program, register 1 contains the address of the B00#SSEC control block.
The B00#SSEC control block contains global security parameters that are common to all Beta products. It is described in the BSA Installation and System Guide. B00#SSEC points to the B97#SEC control block containing Adabas Audit Data Retrieval specific parameters.
Member B97#SEC in your BETA97.SAMPLIB contains a DSECT for control block B97#SEC. The parameter list is provided for user modification of the security exit.
Displacement |
Description |
---|---|
+0 |
Function code |
+4 |
Name address (folder or VCI user) |
+8 |
Name length (folder or VCI user) |
+12 |
Form address |
+16 |
Form length |
+20 |
Extension address |
+24 |
Extension length |
+28 |
Report address |
+32 |
Report length |
+36 |
Jobname address |
+40 |
Jobname length |
+44 |
Index name address |
+48 |
Index name length |
+52 |
Owner address |
+56 |
Owner length |
+60 |
Security level address |
+64 |
Security level length |
+68 |
Table name address |
+72 |
Table name length |
+76 |
Submit user address |
+80 |
Submit user length |
+84 |
Address of Index data |
+88 |
Length of index data |
Please refer to IBM's RACF Macros and Interfaces manual for detailed information.
On return from the exit program, register 15 must contain one of the following return codes, which are the return codes of the sample exit:
0 |
Resource name built correctly In this case, register 0 is set to 0 and the security router (BST00STH) will carry out the RACROUTE for the entity pointed to in register 1. |
16 |
An error has occurred In this case, no RACROUTE will be carried out. A WTO message (IRM0000E ERROR IN B97UXSEC DETECTED. CODE code) on the console helps you find the cause of this error: FU Invalid function (B97UXSEC not up-to-date) 01 Parameter Addr = 0 02 Parameter Length = 0 03 ACCE = 0 (VTAM) 04 Entity too short ( <= 0 ) or too long ( > 64 ) (Entities for NCI documents are automatically truncated if too long) |
32 |
Invalid resource name In this case, no RACROUTE will be carried out. Register 0 contains one of the following information codes, which indicates which resource name is invalid: 1 Name 2 Form 3 Extension 4 Report 5 Jobname 6 Indexname 7 Owner 8 Security level 9 Table 10 Submit user 11 Index data |
The sample exit B97UXSEC checks the Adabas Audit Data Retrieval resource names for the correct format. Database entries which do not fit RACF naming conventions are rejected.
Legal characters for resource names are the alphanumeric characters A-Z and 0-9, plus these special characters:
US |
< |
( |
+ |
| |
$ |
) |
¬ |
- |
/ |
_ |
> |
# |
@ |
' |
= |
" |
UK |
< |
( |
+ |
| |
£ |
) |
¬ |
- |
/ |
_ |
> |
# |
@ |
' |
= |
" |
German |
< |
( |
+ |
! |
$ |
) |
^ |
- |
/ |
_ |
> |
# |
§ |
' |
= |
" |
Codepage 500 |
< |
( |
+ |
! |
$ |
) |
^ |
- |
/ |
_ |
> |
# |
@ |
' |
= |
" |
Hexadecimal |
4C |
4D |
4E |
4F |
5B |
5D |
5F |
60 |
61 |
6D |
6E |
7B |
7C |
7D |
7E |
7F |