Download Control and Monitor Facilities for Multi-User Access

Survey
yes no Was this document useful for you?
   Thank you for your participation!

* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project

Document related concepts

Commitment ordering wikipedia , lookup

Entity–attribute–value model wikipedia , lookup

Serializability wikipedia , lookup

Oracle Database wikipedia , lookup

IMDb wikipedia , lookup

Extensible Storage Engine wikipedia , lookup

Open Database Connectivity wikipedia , lookup

Ingres (database) wikipedia , lookup

Functional Database Model wikipedia , lookup

Microsoft Access wikipedia , lookup

Relational model wikipedia , lookup

Database wikipedia , lookup

Concurrency control wikipedia , lookup

Microsoft Jet Database Engine wikipedia , lookup

Clusterpoint wikipedia , lookup

Database model wikipedia , lookup

ContactPoint wikipedia , lookup

Transcript
Control and Monitor Facilities for Multi-User Access
Randy Horne, Tennessee Valley Authority, Chattanooga, TN
messages of the job. In some cases a wro is sent to the
console if the event being recorded is of system-wide nature.
The second way significant system events are recorded is via
the System Management Facility (SMF)_ SMF record types
have been aSSigned to M UDBACF that contain the data
necessary for auditing accesses, recording statuses and
problem resolution at both the database and MUDBACF level.
WHAT IS IT
This facility is used to control the availability and audit the
access of SYSTEM 2000° databases in a Multi-Usero
environment. The user exit feature of SYSTEM 2000 is utilized
to perform these tasks. During normal processing the facility is
transparent to SYSTEM 2000 users. The facility is driven by a
table of database access profiles. Each profile defines the
access paths (CICS, TSO or Multi-User batch), the number' of
concurrent users and the timeframes or access windows
available for a database. The current access status along with
key historical events are also maintained in each profile. Every
Multi-User system requires an entry for each database to be
accessed.
The availability of a databse is interrogated at
allocate and open time. The audit trail of database accesses IS
produced both in the Multi-User (MUDBACF) and single-user
(SUDBACF) environments.
ERROR PROCESSING
Database errors that are integrity threatening are intercepted
by MUDBACF. The appropriate access prOfile is modified to
ERROR STATUS so that no new processing will be alloWed.
The next available database action is deallocation from the
Multi-User environment. The problem with the database is
corrected in the single-user environment.
This error
interception does not include rollback or any processing return
codes. This error processing stops any recursive abends for a
database processing in the Multi-User environment.
In the Multi-User system a series of CICS transactions provide
menu screens to drive tt'le facility. The facility has 2 command
menus:
DISPLAY FUNCTIONS
The display functions provide information about the access
profile, the users on the database, the internal status of the
database, and the physical status of the files that comprise the
database.
Combination displays provide information about
applications (groups of databases) and overall MUDBACF
status. These displays being inquiry-only are available to a
wide range of support personnel and users.
1) database coordinator functions (database access
profile inquiry and modification),
information center/help desk inquiry functions.
and
2) database adminstrator functions (database and
Multi-User system commands).
DYNAMIC FUNCTIONS
Additional console commands are also provided for database
and MUDBACF status inquiries.
Changing an access profile is provided at both the local and
global password level. The access profile screen provides
change options at the database level. The global control screen
provides change options that can be localized to a database
profile and also system-wide options that affect all access
profile entries.
MUDBACF is not intended as a security package. By its design
as a resource access control facility it has some inherent
security features. It is operationally transparent to all security
facilities in-line between the users and the database. It offers
but does not demand an additional layer of security for
Multi-User database access.
MUDBACF DATA TRANSFER
This additional layer has 2 levels. One is the static or fixed
database access profiles created from a database repository.
The second is the ability to dynamically alter the database
access profiles during Multi-User operation. Both levels are
authorized functions restricted by MUDBACF passwords local
(LPSW) to each entry or DBA passwords global (GPSW) to the
access profile table.
The MUDBACF facility is driven by executing the SYSTEM 2000
ENABLE/DISABLE EXIT command in a plex (CICS transaction)
program. The data passed to the Multi-User region contains
the MUDBACF command, address space identification from the
requesting ASID and return storage address.
WHO IS IT FOR
ACCESS PROFILE PASSWORDS
The data'base C')ordinator (DBC) is the deSignated person with
overall responsibility for a database. The DBC has control of
the static database profile information.
The DBC also has
MUDBACF functions available that allow dynamic .modification
of a access profHe entry. The Systems and Database Support
Staff has OBA and systems responsibilities. AU MUDBACF
capabilities are available to this staff via a global password.
The information center/help desk personnel 'wlll at times need
to know the current status of a specific database. The standard
S2AC transaction is used. but with an inquiry-only password
(IPSW).
lPSW requests are made through the CICS transaction S2AC or
the batch interface program MUDBCNTL
MUDBCNTL is
treated like any other Multi-User batch program in that
manipulation of a specified database is controlled by a access
profile. If a request satisfies the access profile interrogation,
then the MUDBCNTL request is serviced, The GPSW is a
password that can access any database entry in the access
profile table.
The transaction S2SC has all S2AC functions plus the DBA
additional functions. Both are restricted by CICS sign on id.
The IPSW is an information-only password that can inquire into
any entry in the access profile table. It has inquiry status only
and cannot modify any access profile.
The console operator can inquire into the current. status of any
specified database through additional Multi-User commands in
MUDBACF.
These commands interface with the -database
access profile table. Other commands through MUDBACF will
display Multi-User status from a MUDBACF or database access
perspective. These additional-commands eliminate the need for
operations to signon to any subsystem in order to comm.unicate
fully with any Multi-User. The following examples illustrate the
command and response for the new MUDBACF commands.
WHAT DOES IT DO
AUDIT FEATURES
Audit trail for database accesses is accomplished in 2 ways.
First a WTO denoting the event is contained in the system
330
ADDITIONAL
COMMANDS
MUDBACF
F S2KIlUJOB, QUIESCE
Multi·User
CONSOLE
VARY DATABASE OFFLINE
This request will modify the specified table entry to deny any
new users from opening the database for processing. Any
current users will be cancelled. The id of the requestor (CICS
or TSO) will be the only user allowed access to the database.
(AlLOW NO NEil OSERS)
'S2KI'IUJOB: JlUDBACF ACCESS PROFILES QUIESCED
'S2KI'IWOB: END REQUEST
VARY DATABASE ONLINE
(ALLOW NOR"Al PROCESSING)
F SlKIlUJOB. RESUI'IE
tSZKI'IUJOB: IruDBACF ACCESS PROFILES RESUI'IEO
This request will modify the specified table entry to allow
normal database access subject to other profile settings.
2B FR.! 21 :06: 11
'S2KIWJOB: END REQUEST
F SZKPlUJ08, STATUS
(PROFILES THAT ARE LOCkED. DEAlLOCAT£D, GFFLlNEl
'SZKI'IUJOB: IWDBAtF STATUS NOl!IIAl
'QKPlUJOB: UND-DATA
AVAILABlE
'S2KI'IWOB: EJIP~I'IEDICAL
ISZKIIlUJOB, nAIN1NG
IS2KIlUJDB: END REQUEST
ADDITIONAL DYNAMIC OPTIONS
18 NED 14:12,01
DEALLOCATED
OFFLINE
OPEN
LOCKED-CaIZ OPEN
II NED IS:!I:45
18 WED 13,00:43
18 NED 14::27:01
ALLOW/DENY Multi-User BATCH TIMEFRAME
This request will modify the specified table entry to either deny
or allow the specified database to be available for access by
Multi-User batch programs. Additionally, speCific times can be
set for defining the available window for Multi-User batch
access.
F S2Kf'lUJOB. OB",PONER-i>ROD
ISZICIIUJOB: POWER-PROD
AYo\llABlE
IS2KftUJOB: INTEGIUTV, UHOf'EKED
DEALLOCATED
21 SAT 10:111:56
APPLICATION: afC GEt4
1$2I(IIUJ08: fiLE, I DSG: USER.DATABASE.FIlE.GENERIC
IS2JU'IUJOB, DBC: JOE PROGRAMER.
1S2I(I'IUJOB: AHC, lEEPER 15'100
'S2:KI'IUJOB: END REQUEST
F S2KIWJOB, Af'P"PERSONNEL
F S2I(I'IUJOB, OO=FHOS
FH05
ALLOWJDENY BATCH INTERFACE TIMEFRAME
This request will modify the specified table entry to either deny
or anow the specified database to be available for access by
the batch interface to MUDBACF. Additionally, specific times
can be set for defining the available window for interface
access.
(ALL ASSOCIATED [lATABASESl
IS2K1'1WOB: E""LOrtES
tS2KI'IWOB: RETII~EES
IS2KI'IUJOB: END REQUEST
1S2I(I'IUJ08:
IS2KI'IUJOB,
1S2I(I'IUJ08:
1S2IU'1UJOB:
PHONE, 16:5) U2-1180
PHONE, (US) 632-9nl
AVAlLABLE
A"'A1LABlE
OPEN
UNACCESSED
22 SUH 01,0,)-:22
22 SOH 11,31,30
ALLOWIDENY SCF TlMEFRAME
(ACTlVE USER DATAl
DE4a
EflPLOVEES
EI'IP-I'IEDICAL
ENlI REQUEST
BETTV JO EHOOSER
AYAILABLE
OPEN
AVA1LABLE
!PEN
This request will mOdify the specified table entry to either deny
or allo'w the specified database to be available for access by
SCFo processing. Specific times must be set for defining the
available access window. Allow defines the inclusive times and
deny defines the exclusive times available for processing.
24 TUE 06:04,34
24 TUE 0(, :04 ,42
MUDBACF REQUESTS
DISPLAY DATABASE STATUS
ALLOCATE DATABASE
This request will display key data fields of the current master
record in_main memory. This request is valid only for open
databases. There are 2 screens of output. The first screen is
static status data. The second screen contains the dynamic
data associated with the processing of the database files. the
second screen is refreshable with current pages in use,
characters in use and accumulated iJos .
This request will result in allocation of the specified data base
to the MUlti-User system jf:
.. the database specified is a valid entry in the
access prOfile table,
.., the database specified is not in a lock status,
.., all of the database files exist,
and
... the database is not in use by another job.
GLOBAL FUNCTIONS
Failure of any of these conditions will result in the database not
being allocated followed by the appropriate return code. Also,
any faifure will produce an audit trail record.
Either a
successful ALLOCATION COMPLETE or an ALLOCATION
FAILURE wto will be issued to the program log and to the
system log.
LOCK DATABASE
This request will place the specified database in a LOCK status.
No new user activity is allowed to start on the specified
database except for logical andJor physical close.
Current
users ate permitted to continue. The global password holder
now has complete control of this database.
All MUDBACF
commands are available to the GPSW but only inquiry
commands are available to the LPSW.
DEALLOCATE DATABASE
This request wjll result in deallocation of the specified data
base from the Multi-User system if:
UNLOCK DATABASE
.., the database specified is a valid entry in the
MUDBACF table,
.., the database specified is not in a lock status,
and
.. the active user count fs zero.
This request will return the specified database to a DBC/user
access available status.
QUIESCE ALL DATABASE ACTIVITY
Failure of any of these condItions will result in the database not
being deallocated followed by the appropriate return code.
Also, any failure Will produce-an audit trail record.
This request will place the all databases ina QU I ESCED status.
No new user activity is allowed to start on any database except
for logical andior physical close. Current users are permitted
to continue. The global password holder now nas complete
access control of all databases.
Only MUDBACF inquiry
processing is available to LPSW holders.
If the database is in use, it will be marked PENDING, the active
users cancelled, then the database is deallocated. No new
access IS allowed to start on a PENDING DEALLOCATION
database.
RESUME DATABASE ACTIVITY
Only the deallocate command or system shutdown wj1J
physically close a database. The active use count at zero will
not physically close a database.
This request will return all databases to a DBCJuser access
available status. Any individual databases that were in a LOCK
status remain ~n a LOCK status.
331
JOURNAL ACCESS PROFILE TABLE
ACCESS STATUS
This request will write each entry in the access profile table to
the SMF log.
I'IULTI-USER DATA BASE Aca;ss COIITIlOl fACILITY (MJDBACF)
SlKxxlO(x
INNNNN
(PUID
DISPLAY ACCESS PROFILE ENTRIES
DISPLAY ALLOCATED DATABASES
DISPLAY ACTIVE DATABASES
ACCESS STATUS
HH,I'IIII,SS
'''''DD/Y'I
TEIII'IID
DATA BASE MAIlE
APPLICATION
ACCESS STATE, _ _ _ _ _ __
PHVSICAl IFEN UST ACCESS ACCESSOR TRNIIJPGIII
KH:I'III:SS
TERIIIID
TRA.lVPGII
HH:NI:SS
DOD Nt!
RACF 10 NAIIE.
DOD 11M
OAI'IAGf SWITCH
AllOWED IIMII M:Tl'WE Of IIAK nn"n
PLEK ACCESS,
SCF ACCESS:
$lOTTO nMII ACTIVE OF IIAX IInnn
TSO ACCESS,
DENIED n",," ACTlYE OF IIIAII II11nn
IIIULTI-USER BATCH ACCESS, :;.LOTTED flnnn ACTIVE OF flAX nnlln
ALLOCATE
HH:IIIII:SS
DOD NN
This request will return in access profile format each of the
valid entries in the access profile. The entries are returned
sequentially beginning with the first entry in the access profile
table. Variations are the selection criteria of allocated, active
or all access profiles.
CHANGE LOCAL PASSWORD
DEALLOCATE
HH:I'IIII,SS
DOD NN
IInnll
nllll.llnn.nnn HH,IIIII:SS DOD NN
ACTIVE USEIiS:
ACCESSES HilS SESSIOO,
This request will modify the current LPSW for the duration of
the current Multi-User session. The new LPSW is available
only from the DBA who changed the LPSW and is not displayed
except by GPSW requests. This change can be made at any
time with the GPSW.
Pfl=<HELP> PF2=<SlAC> PFl,,<;fXIT> PF4=<DBST> PF5=<TPUS> PF6=-::IIUaJ>
PF7=<Dil;P> Pf8",<DVNA> PF,=<ctm.> PflO='~NU> Pfll=<---> Pf12:<EXEC>
--- JNFD/ERROA-PiESSAGE------------------------------------
D1SP
ACCESS PROFILE
flULTI-USER DATA BASE Aca:SS CONTROL fM:IllTV (IIIUDBACF)
MUDBCNTL
S2Kxxxxx
IN/-INNN
CPUID
This program executes as a Multi-User batch job. Its function
is the same as the CICS MUDBACF transactions except for the
display options. It is called by a user-written program that
passes request parameters to it. Request return codes are
returned to the calling user-program for action. The most
frequent use of this interface is to allocate or deallocate a
database in Multi-User. The Multi-User batch access control
profile for the database must allow Multi-User batch for this
request to work.
MUDBCNTL must be linked with the
user-written program which passes the MUOBACF request, the
database name and the access profile password for servicing.
I*I,M:SS
IIIII/DllIYV
TERIIID
ACCESS PROFILE
DUA BASE NAftE
APPLICATlON
GENfIllC NAM, _ . _ _ • _ _ . _ . _ ._ _ . _ . _ . _ fiLES:
ALLOCATE
_ DEALLOCATE
_ 'WARV ONlINE
_ VARV OFFLIKE
_ ALLOCATE IF DAIIAGED _ INITlM.. ALlOCUF. _ _ _ CANCEL IJ:EII
TP BATCH,
IIIAK ftllM A/D •••• _
TO _ _
TP SCf,
!fAX nnnn AID •••• _
TO _
IIUlTI-USER BATCH,
l'loU nnnil AID •••• _
TO _ _
TSO,
IIAK nnlln AlII....
TO
BATCH INTERFACE ACCESS.
AID....
TO
DATA BASE COORDltfA,TDR: _ . _ _ . _ ._ _ • PHONE: (AU) PPP-NNNN
AFTER HOURS CONTACT,
_ . _ _ . _ . _ . PI1ONE, UAA) PPP-NNNN
IIODIFlED, TERIIINALID
HH:IIII:SS DIKI ION
RACF.ID.NAI'IE ••••••••
PF1=<HELP> Pf2;<S2AC> PF1~<£KIT> PF4:<DBST> P!'§,,<TPUS> PH~<I'IUaJ>
PF7:<DlSP> PFB=<DVNA> PF'=<CHTl> PF10=<ItENU> PFll=-<---> PFIZ=<EXEC>
MUDBACF SCREENS
- -J NFD/ERROR-fllESSAGE-------------------------------~----D'INA
SIGNON
DATABASE STATUS
II/
~,,=//
IIIUDS
== "'=//
:=II///=-=-/
===""=======/
::/
==/
===1
;==/
/1/1//1
,,~====/
==-/
""/
=-=/
==/11111
-=,,====/
1111111
IIffll
==,,==-=1
=====1/· ==/
///////
===-;:;/
=-=/
==-/
=-=/
:=11111/
=="'=~=/
//1///11 /11/11
,,=-""""-=-=/ :;:::/
==/1/
=/111
"-==-=1
=====/
====1
====1
==/1111/ 1/11/=1
=======/ =:==:/
1/1
II/ 1111111/ /111111
==1 "'==-===-=/ ======11
==/
==/ ==1 ===/ ::!
=-/
:=11//1=1
==/
==/ ~=/ =;/:/ ==1
=/
=======/
==1
::/ =:1 ==-/ =/:=/
=/
=:/ ::1/
=-=-////11 =:///==1 ==/
-="'/
=!
==/
"-=/
======1 =,,===/ ==/
=-=!
:/
==/
==/
///1/1
="'''-''':/
-=/111
=====/
=="'=/
11/11=1
IIULTI-USER DATA BASE ACCESS CONTROL fA.CILlTY (IIUDBACF)
$2jr(xxxxx
tNNNNN
CPUID
DEFINITION: nnn,nM
LAST SAVE:
Y£RSION: n¥v/ectC
DATA CVClE:
ROLLBACK, xxxxxxxxxx
' ' ' """MI'I
---1 tlfD/£RROR-"ESSAGE----------------------------~-----------
""
LEY£LS: n,IInn
FUU PASS, xxx
SECURITY BV ENTRV: xxx
IlULTlPLE HOLDS: xxx
TP USERS
I'IULTI-USER DATA. BASE ACCESS CONTROl FloClLlTV U(UDBACF)
PlULTI-USER DAIA BASE ACCESS COtlTROL fACllITV (I!UDBACF)
S21(xxxxx
INNNNN
CPUID
Htt ,11111 ,SS
""/00/'1'1
TERI'IID
SELECTlOtl IPTIONS
ROLLBACK LUX, nnnnnn
PF1-=<HElP> PFZ=<S2AC> PF3"<EKIT> PF4:<IIBSZ'> PF5=-<DSST> PH==<---->
PF1:<DISP> PF.,,<DVHA> PF9::<CNTl> PFlO=<IIENU> PFll=<---> PFl2=<EI(EC>
--- JNFO/ERROR-IIESSAGE---------------------------------DBST
Pfl=<tiELP> PFZ=<SZAC> PH:<EMIT> PF4=<ALLP> PF5,,<----> PF6,,<---->
Pf7=<DlSP> Pf8=<DYtlA> PF9=<CtlTL> PflO=<IIIEHU> Pfll=<----> PFl2HEXEC>
MENU
DAllAGE, xxxxxxx
""/DD/V'I-HH : 1111: SS
NEXT !.PDUE LOG IoCTlVITY: xxxxxx
COI'IPONENTS, nn,nnn
PASSWORDS: nnlln
nn,nnn.llnn
ROLLBACK PCT: nil"
UP DATE LOG, xxxxxxxxx
FACILIT'I
TER~ID
TlNESTAIiIF': IIII/DD/YV-HH,II":SS
DUA CYCLE: nn.nnll,flnn
1II1IlTl-USER SVSTEII IS S2Kxxxx li' 1I0tlITOR IS CICSxxxx CPU IS XKXll
ACCESSltlG TERlllltlAL IS )lMKMMl(l(X USER IS l(l(KXl(l(l(l(l(XXXXlCXKXXMI(
T1~ESTAJIIP lS HH,III111,SS ON DDDDDDDDD
DO VVVV AUTH{ •••••• )
SZKxxXXx
ItlNtltlN
CPUID
11111/00/'1'1
DATA BASE twa:
APPLICATION
=-="'=-"-/
/Il/If /11
=====//==1
==1 ==/ ==/
=:/ ==/ ==/
==1 ==1 ::/
==///==/ ==11//
=====/ -====:/
I*/:IIIII,SS
DATA USE STATUS
TP USERS
DATA BASE NAI!E
APPLICATION
tIH,,,,,:SS
!III/DDIYV
TEIiJIIID
DATAUSE mll£,
"
A?PlICATlOtl HAlliE, _ _ _ __
PASSWORD,
DISPUY SINGLE USER, _ _
DISPLAV fUtlCTlDtlS
DVNAIIIIC fUNCTlmlS
ACTIVE USERS, nnlln
C(lNTR(ll FUtlCTlONS
TP: nnn
ACCESS COUNT: nltn,nnn,nnn
CANCEL SPECIFIC USER:
TPBATctI: nnn
"UBATC!!: nnn
TSO:
PHVSICAlIFEM, HH,I!I'I,SS-DDD tIN
PFl=<HELP> Pf2=<SZAC> PF1=<EKID Pf4=<lWaJ> PF5",<AIJSIt> PH=<-->
Pf'7=<Dl::f'> PfB=<DVNA> PF'=-<CNTl> PFlO=..::JtEMU> PFll:<REFR> Pf12=<EXEC>
---I NFD/ERROR LlifSSAGE------------------------------------TPUS
PF1=<HELP> PF2,,<!;2AC> PF3=<EKIT> Pf4=<--__ > PF5=<----> PF',,<---->
PF7=<DISP> PF8=<DVNA> PF9=<CNTL> PF10=<lIfNlI> Pfll=-<----> PFl2=<EKED
---INFO/ERRDR-I'IESSAGf------------------------------------------
"'"
332
MULTI USER BATCH
GLOBAL CONTROL
IIUlTl-IJSEIl DATA BASE ACCESS CONTROL FACILlTV (JlUDBACFl
IlULTl-USER. DATA BASE ACCESS CONTROL FACILITV IIWDBACfl
SZKxxxxx
INttNNN
!'IULTI-USER BATCH
CPUID
S2KxxXxx
t\H,I'I11,SS
I'IR/DD!YY
TER"lD
DAH. BASE HAlliE
APf'L1 CA Tl ON
GLOBAl CONTROL (J>TlQNS
HH:M:SS
IIfI/DD/YV
TER"'JD
INNNNN
CPUlD
SYSTE" WIDE fUNCTlONS:
_ QUIESCE !'IULll-USER ACCESS
_ DISPLAV ACCESS PROfILES
DISPLI.Y ACTlyE DATABASES
DISPLAV SPECIFIC USER,
ACTIVE USERS, nnnn
DHABA~
JP, nnn
WBAlCH, nnn
PlUBATCK: nnn
SPECIFIC FUNCTIONS,
_ LOCK DAHBASE
lSD, nnn
_ CLEAR
ACCESS COUNT: nnn,non,nnn
DAlABA~
LOCAL
PF,>cS2AC>
PF1:~DI:;P) Pf8:~DVNA)
UNLOCl DATABASE
CHAN&E LOCAl PASSWORD
USERS
PHYSICAL OPEN: HH:III'I:SS-ODD NN
GL~:!~B:!~s:6:~~
Pfl~<HELP)
RESt./IIE II.Ul T1-USER ACCESS
JOURNAl ACCESS PROFILES
DISPLAV ALLOCATED DATABASES
------
PA~SI«JRD:
PF3~<fXlT>
PF4:<AU5R> pF!i:(----) PF6=(----)
PF'=<CIHl> PFlO:<I'IENU> Pfll=<REFR> pFl2=<ElCED
PFl=<HElP> PF2=<SZAc> PF3=<E1UT> Pf4=<All.P> PF5:<---> PF6:<---->
P-Fl=<DlSP> Pf8:<DYNA> PF'=<CNTL> PFJO=<1IflfU> PFll=<---> f"F12:<EXEC>
- - INfO/ERROR-"ES5AGE-------------------------------------CNTl
---1 NFO/ERROR-I'IESSAGE----------~--------------------------------
"'"
ACTIVE USER
PROFILES
IIULTI-USER DATA BASE ACCESS CONTROL FACILITY (IIUDBACF)
l'ItlLTl-USO DATA BASE ACCESS CONTROl. fACILIJV (IIUDBACfl
SZKxxxxx
INt&NNN
ACTlVE USER
CPUID
HI""IiI:S5
M/OD/YV
SZl()(xxxx
INMNNN
CPUlD
TERIUD
DATA BASE HAl'If
APPLICATION
TERI'I]NAlIJOBNAPlE:
n:ANSACTlOH/ACCtlUHT:
USER:
SIGN ON DATE AND TlIIE: III'I-D[l--VY HH:"",:;S
ElAPSEtl TlI'IE CLOCK AND CPU, nnnnnnnn nnnnnMnnn
PROflLES
SEL DATABASEHAM:
HH:I'Ut:SS
II.II./DIl/YV
TERIII0
APPLlCATIOM
STATUS
I'Ut,SS,lIlOK
S2K CALLS' nnnnnnnn
DAY-A BASES Cf'EN, " "
DATA BASE,
SIGN ON DATE AND Tll~E, JII"-Db-VV HH,,,",,SS
ELAPSED Tll'IE, HII:fII"',SS
DATA BASE I/O ACTIVITY, nnn,nnn,nnn
PFl~<HELP> PF2~<S2AC> PF3,,<UlT> PF4=<TPUS> Pf5=<II.U8J> PF6=<---->
PF7=<DISP> PF8=<DVNA> PF'=<CNTL> PflO=<JIIENU> Pfl1=<REFR> PFl2=<EKEc>
- - l NFO/ERROR II.ESSAGE-----------------------------------------AUSR
TJIl.ESTAIP
HH,IIfI,SS NN
KH,JIIfI'S$ NN
Htl,IIfI:SS ION
HH,II.II.,SS NN
IUhllfl,SS HN
Htl,,,-,,,SS HN
HH:"II.,SS HN
HH,"",$S MN
HN,II.II,SS NM
HH,"",SS NN
""1'1
11.1'11'1
"""
II.fIIl'I
"""
1'11'111.
"""
1'11'11'1
1'1,,11.
fIIl'I"
("ORE)
PF1=<HELJ» PF2=<SZAC> PF3:<EXll> PF4=<----> PF5=<---> PF6=<I'IORE>
PF1:<DISP> PF8=<:IlVNA> Pf9=<CNTL> PflO=<II.EHU> PFll:<----) Pf12=<EXEC>
I NFO/ERROR I'IESSAGE--------------------------------------ALLP
DATABASE SIZE
l'IUL T1-USER !lATA BASE "CCESS CONTROL FACILlTV (II.UDUCf)
SZKlCXXlCX
INNNNN
a>UID
FlLE
DATA BASE SIZE
Wl:"''':SS
IVI/DO/VV
PAGES
ALLOCATED
DATA BASE NAII.E
APPLICATION
PAGES
l PAGES
IN USE
IN USE
nnn ,nnn ,nnn
nnn,nnn,nnn
nnn ,nnn ,nnn
nnn ,nnn ,nnn
nnn ,nnn ,nnn
nnn ,nnn ,nnn
nnn ,nnn ,nnn
nnn ,nnn ,nnn
nnn ,nnn ,nnn
nnn ,nnn ,nnn
nnn ,nnn ,nnn
nnn ,nnn ,nnn
nnn,nnn,nnn
nnn ,nnn ,nnn
nnn ,nnn ,nnn
nnn ,nnn ,nnn
n ,nnn ,nnn ,nnn n ,nnn ,nnn ,nnn
ACCESS COUNT,
nnn,nnn,nnn
IInn.n
nnn.n
nnn.n
nnn.n
TER!'IU
CHARACTERS
IN USE
nnn ,nnn ,nnn,nnn
nnn ,nnn ,nnn ,nnn
nnn,nnn,nM,nnn
nnn ,nnn ,nnn ,nnn
nnn ,nnn ,nnn ,nnn
nnn ,nnn ,nnn ,nnn
nnn ,nnn ,nnn ,nnn
nnn ,nnn ,nnn ,nnn
nnn ,nnn ,nnn .nnn
MUDBACF EXIT LOGIC FLOW
FILE
I"
+----------------+
nnn ,nnn ,nnn
nnn,nnn,nnn
nnn,nnn,nnn
I
I EXIT 02
+--------------+
+----------------+
DDNAI'IEnn,
I
I
I
J TERMINATION
EXIT 01
I
+-----------+
I MUAC
I------IEXIT 43
1 MOD I FICA TI ONS I
1CONSOLE
I EXIT 41
1 INQUlRY
I
I
1COMMANDS
ROLLBACK
+----------------+
+-----------------------------+
1
DATABASE ACCESS REQUESTS
I
I
ACCESS PROF! LE TABLE
1
1-----------------------------1
1 OPEN I PROCESS I CLOSE 1
1------------------------ -----1
IIULTl-USER DATA BASE ACCESS CONTROL FACiLITY lIIUDBACF)
HH:"",SS
""/DO/W
TERIIID
DATA BASE NAI'IE
APPLICATION
I BATCH
I
I I NTERF ACE !
+---------------+
I EXIT 42
I SYSTEM
FRO'" ALLOCATION AT HH,IUI,SS-DDD NN
IU.TASET STATUS
+----------+
1 READ PROFILES
nnn ,nnn ,nnn
nnr- ,nnn ,nnn
nnn,nnn,nnn
nnr. ,nnn .nnn
DATASET STATUS
INNNI#!
Cf'Ultl
--> INFOI
I S2SC --> DBA I
I
nn~,nnn,nnn
PFl=<HELP> Pf2=<S2AC> PF3=<EMIT> PF4=<DBST> PF5=<DSST> fF6~<----)
PF7=<DISP> PF8=<DVNA> PF9=<CNTL> PFIO=<fIIENU> PFll=<REFR> PFl2=<EJ(Ec>
---l NFO/ERROR-I'IESSAGE----------------------________________ --------DBSl
52:"'"'"",,>;
S2AC --> DBC I
!EXITOO
!
I Multi-User
I
I INITIALIZATION I
ACTIVE USER TABLE
X"XlClClClCXlClCXlCXXlClCXXlClClClCXXlClCXXXlCXXXX~XXXXXXxx
SEQ'
01
.02
.03
.O~
YOLUItE
KJ(XKXX
KKKJ(J(K
KKXKXX
XXK)(XX
ADDRESS
MJ(XXK
K)(XKK
j()(J(J(J(
J(KJ(KJ(
STATUS
KJ(XM
KXMK
KKKK
J(KKK
EXTENTS
1
OPEN
CREATE, PlI'IIDD/VV DSORO: J(J( "LLOCATlON: (PI nnn,nnn IS) nnn.nnn
PAGE SIZE, nnn,nnn IYOlU"E$: XKJ(
RAer: KKK
DISPOSITION: J(KK
DEVTVPE: KKKXKX
FILE 1/0'S: nM,nnn,nnn
ALLOCATED, HH,I'III.,SS-DOO NN PHVSlCAL OPEN, HH,II.III,SS-OOD NN
RESOURCE USE
I
CLOSE
1--------------1
t EXIT 21
I
+-- ------------+
+----------+
TRACKS
nnn ,nnn
nnn ,nnn
nnn
1---------1
1----------1
I EXIT
I EXIT 25 I
1 EXIT 36
I
1 EXIT 04
I
03
1
I EXIT 07
1
+----------+
Pf1~-::HELP> PF2=<S2AC> PF3~-::EKlT> PF4=<DBSZ> Pf5=~DBST> Pf6,,<II.ORE>
PF7:<DlSP> PF8"<DVMA> PF~=<:CNTL> PflO=<PlEHU> PFll:<---> PFl2:,,<:EJ(EC>
---INFO/ERROR f'lESSAGE--( I'IORE THAN 04 YOLU"ES ••• Pf6)------------IlSST
333
I
J PHVSlCAL 1
1----------1
t
LOGlCAL
+---------+
I
PHYSICAL
1
EXIT OPERATIONS
Acknowledgements
Several user exits are used for MUDBACF execution but the system
is basically passive. Only a few instructions are executed in
MUDBACF for each user during normal processing. Physical allocation
and deal1ocation require more instructions as does error processing.
MUOBACF requests execute varying numbers of instructi'ons based on
the specified command.
°SAS, SYSTEM 2000 are registered trademarks of the' SAS
Institute, Inc. Cary. NC. Multi-User. SCF and Coordinated
Recovery are trademarks of the SAS Institute, Inc.
Author
EXIT 00 EXIT INITIALIZATION
If you have any questions or comments, please write or call:
Exit 00 initializes the user exit table for SYSTEM 2000. Additional
MUDBACF modules to support exit operations are also identified at
this time
Randy Home
Tennessee Valley Authority
150 West 11th Street
MP 2B-C
Chattanooga. TN 37402
(615) 751-2432
(615) 751-3163 fax
EXIT 01 MUDBACF DRIVER
Exit 01 is normally used to control the availability of user exits.
This function has been transferred to EXIT 00. Through the
ENABLE/DISABLE ROUTINE command, this exit communicates with the
CICS, TSO and Multi-User batch interfaces for MUDBACF.
EXIT 02 MUOBACF INITIALIZATION
Exit 02 builds the internal access profile table from the system-wide
access profile file.
EXIT 03 PHYSICAL OPEN (prior to)
Exit 03 interrogates the access profile table for valid access
conditions. If successful database allocation is requested.
EXIT 04 PHYSICAL CLOSE {after}
Exit 04 deallocates the database after a deallocation request or
system termination.
EXIT 07 PHYSICAL OPEN (after)
Exit 07 records database status at open time and updates the active
user table.
EXIT 21 RESOURCE UTILIZATION
Exit 21 compares user performance against installation performance
objectives.
EXIT 24 PHYSICAL CLOSE (prior to)
Exit 24 records database status at close time.
EXIT 25 LOGICAL OPEN
Exit 25 interrogates the access profile table for valid conditions
and updates the active user table.
EXIT 36 PHYSICAL CLOSE (prior to)
Exit 36 interrogates the access profile table for valid database
close conditions and updates the active user table.
EXIT 41 ROLLBACK (after)
Exit 41
rf~cords
Coordinated Recovery" events for.a database
EXIT 42 SYSTEM TERMINATION
Exit 42 records MUOBACF data for a Multi-User jol>.
EXIT 43 CONSOLE COMMANDS
Exit 43 examines operator console requests to MuJli-User and
executes those for MUDBACF.
334