So, my opinion Once a dataset is in the linkst - depending on how it is controlled - someone could put other code in there that is not system friendly.
So I have dataset, MYHLQ.USER.LOADLIB in the linklist. Now it is apf authorized. I use a package like Changemen to deploy to it, but it does not know what should not go there. I use all valid naming conventions for the process. But the code could be something "special". So USERA decides to create a program with an assembler subroutine that can filter data in a database and send to an unknown site. Or set up other issues in the system. USERA has the authority to deploy to that dataset. But who is controlling the source to ensure it does not do bad things. Just my thought Lizette > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of R.S. > Sent: Tuesday, December 19, 2017 6:08 AM > To: [email protected] > Subject: Re: Cobol upgrade 6.2 linklist > > What is the risk of putting COBOL-compiled code into LINKLIST? > Let's assume LNKAUTH=LNKLST. > Such code will not perform any authorized instructions. It can be called from > another AC=1 code, but the problem is the module, not the COBOL code called. > What I'm missing? > > > -- > Radoslaw Skorupka > Lodz, Poland > > > > > NFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
