Protecting Resources › IBM DCE, SystemView, Netview, and OPTIME Protection

IBM DCE, SystemView, Netview, and OPTIME Protection

A mainframe can participate in a DCE environment using OpenEdition/DCE support. DCE programs and data can reside on the mainframe under OpenEdition.

A DCE segment of an ACID allows the fields:

• UUID
• DCENAME
• HOMECELL
• HOMEUUID
• DCEFLAGS
• DCEKEY

Examples: protect DCE

This example protects the DCE:

TSS ADDTO(acid) DCENAME(jordanm)
                DCEFLAGS(AUTOLOGIN)
                UUID(00000075‑71db‑21cf‑b500‑08005a470ba1)
                HOMEUUID(abbc323c‑5ce2‑11cf‑a61e‑08005a470ba1)
                HOMECELL(/.../cis_test1.cis.dog.com)

In this example, the ACID lists a DCE segment:

TSS LIST(acid) SEGMENT(DCE)

SystemView Segment Protection

The SYSMVIEW resource class protects SystemView segments. The keywords allowed with this segment when permitting it to an ACID are:

• APPLDATA
• SCRIPTNAME
• SCRIPTPARM

Example: protect SystemView

This example permits an ACID to this segment:

TSS PERMIT(jordan) SYSMVIEW(A01ITSO.SYSTEMA) 
                   APPLDATA(ptkt1)
                   SCRIPTName(tsoscript) 
                   SCRIPTParm(tsoparm)

NETVIEW Segment Protection

CA Top Secret protects NETVIEW segments. The fields associated with this segment are:

• NETVCONS
• NETVCTL
• NETVIC
• NETVDMNS
• NETVMSGR
• NETVNGMF
• NETVOPCL

There are three new resource classes: RODMMGR, NETSPAN and NETCMDS.

CA Top Secret naming of the NETVIEW fields varies from the IBM NETVIEW documentation.

The NETVIEW fields have the following format:

TSS ADDTO(acid) NETVCONS(consname)
                NETIC(initial.command)
                NETVCTL(SPECIFIC|GLOBAL|GENERAL )
                NETVDMNS(domain1,domain2,...,domain‑n)
                NETVOPCL(n1,n2,...,n99) &lb.n can range from 1 to 2040&rb.
                NETVMSGR( YES | NO )
                NETVNGMG( YES | NO )

Example: protect NETVIEW

This example illustrates an ACID list NETVIEW segment:

TSS LIST(acid) SEGMENT(NETVIEW)

The OPTIME Field

In CICS the OPTIME field matches the TIMEOUT field described in IBM CICS documentation.

This field has the following format:

TSS ADDTO(acid) OPTIME(hhmm)

OPTIME controls the period of time allowed before CICS considers a terminal user to be “time‑out”. The action taken by CICS depends on a CICS parameter SIGNOFF specified in the typeterm definition.