Get me an Exit

[Steve Blackett]

Firstly, I've tried but can't find any "useful" documentation about this.

 

The ENDEVOR exit blocks contain a large copybook defining the in's and out's of what's happening. (COBOL: EXITBLKS)

I am specifically looking at EXIT2 (the pre SCL exit).

 

There are 17 values of the ECB action code (numbered 1 to 32), I am thinking maybe 9 and 10 were deprecated in a previous older version. What I am trying to test is VALUE 14 (known as ENVRNMGR or ENV-MGR-ACTION in COBOL).

 

I thought probably from the name it was a type of thing done in an environment (like creating a type) - but I can't get the exit2 to pickup on anything I would consider an admin/environment piece of SCL (I attempted a few different things, but realised I was just guessing).

 

Does anyone know what this value relates to and what specific SCL invokes it?

Is it even valid for EXIT2 or is it really (from our research called under EXIT7) ?

------------------------------
DevOps Specialist
HSBC
------------------------------

[Guy Derkinderen]

Hello Steve,

Your guess was correct, ECB-ACTION-CODE 14 represents an environment-related action like defining a system, subsystem, etc. In short, any action that updates an entity in the MCF's.
ECB-ACTION-CODE 14 is used only when calling exit 1, the security exit. That explains why exit 2 didn't pick up anything ...

Regards,
Guy Derkinderen
Endevor development
Broadcom

[Russ Gunter]

Steve,

 

In my experience EXIT2 is only concerned with Action Initiation.

I see what you are saying about action 14 in the exit section of the book but I don't see anything concerning a sub-action which type definition would be to the ENVRNMGR action.

 

Rather than an exit it would make more sense to me to add it as a security rule for example Package is the Menu item/Action and BUILD is a pkg sub function

ENVRNMGR is a Menu Item/Action and DEFTYPE could be a sub-function security rule.

 

In the meantime perhaps Dan Walther could share how table tools works and even provide documentation.

I don't believe it documented in the ENDEVOR Guide. Table Tools has a lot of functionality.

However Dan put some excellent information in CSIQCLS0(ENBPIU00). This may be the only documentation other than the Best Practices Implementation information in CSIQSAMP(@OPTION)

 

As you know with DT (Deploy to Test) creating a Sandbox permits someone other than an Admin to create more types and other admin.

I know that in the CSIQSAMP lib member @8DEFTYP appears to be using table tools.

 

Additionally using Program Pathing in security you could allow admins and other specific people to execute the batch admin program but if I was going to do that I would have the program call ENBE1000

then have some type internal table that would permit only those individuals to submit type def cards. 

 

This may be more than you were seeking but I got on a roll.

 

Russ Gunter

CA Broadcom Consultant

Internal Revenue Service

Cell: [phone]

(TOD) Mon –  Fri  7:45 AM - 4:15 PM Eastern

 

"Never forget, 'Some gave all, All gave some'"

"It is amazing what you can accomplish if you do not care who gets the credit", Harry S. Truman

 

Planned days away, 6/17 &18

 

[Steve Blackett]

Thanks for the replies (Guy & Russ).
That makes a lot of sense, it would be good to be documented to explain this.

I have now moved on (maybe backwards) to option 13, Override Signout. I thought this was just an option on another piece of SCL, like a retrieve or generate and there isn't a primary batch option for this either. Is this a code that can be obtained from some direct SCL?

I have experimented with Signin SCL and it's override signout option but it is always presented to EXIT2 as option 12 (Signin).

------------------------------
DevOps Specialist
HSBC
------------------------------

[Sam Beckwith]

Hi Steve,
Apologies for the insufficiency of the documentation. I'll talk to Guy and add an improvement in this area to the backlog.
All the best,
Sam Beckwith
Technical Writer