Subject: RE: Deleting User from CICS/TS
From: Randy Evans (revans@viaserv.com)
Date: Tue Jul 08 2008 - 19:41:41 EDT
Are suggesting that the passwords themselves are maintained in BSTCNTL because of this information? If so, then I disagree with that specific conclusion. The BSTCNTL contains control information that governs how the passwords are maintained as documented in the references you provided, but not the actual user passwords themselves. If you find evidence to the contrary, in either the documentation or actual contents from your IESCNTL or BSTCNTL files I would be very interested in hearing about it. Randy Evans, Viaserv, Inc. > -----Original Message----- > From: owner-vse-l@Lehigh.EDU [mailto:owner-vse-l@Lehigh.EDU] On Behalf Of > Jan Canavan > Sent: Tuesday, July 08, 2008 5:29 PM > To: VSE Discussion List > Subject: RE: Deleting User from CICS/TS > > > > I also found this: > > Ensure that you have removed the // EXEC IESIRCVT statement in the > procedure USERBG.PROC. To do so, use skeleton SKUSERBG (located in ICCF > library 59). If this statement is contained in USERBG.PROC, the settings > specified by the PERFORM PASSWORD ... command will be overwritten by the > IESIRCVT settings! > > > and note there is a > > STATUS | ST Command Use the STATUS command to obtain the status > information of the BSM. Here is an example of using the STATUS command and > the output it produces: > > > This is on page 213 of the manual, and pdf 237 > > Jan Canavan > j_canavan@earthlink.net > VSE/VM SYSTEMS PROGRAMMER
This archive was generated by hypermail 2b25 : Sun Jul 27 2008 - 05:20:09 EDT