Application Modernization

Hello Rocket Community,We are migrating CICS applications from z/OS to Rocket Enterprise Server and have a custom security solution implemented in assembler that performs user authentication, authorization checks, and application sign-on processing through RACF.Our approach has been to convert the assembler modules to COBOL, preserve the existing application sign-on flow, and replace the RACF dependency with Rocket Enterprise Server ESM integrated with AD/AD LDS.Has anyone implemented a similar approach?Specifically, we're interested in:Preserving existing EXEC CICS SIGNON or related security calls. Minimizing application changes while maintaining existing authorization behavior. Lessons learned, challenges, or recommended alternatives.Any feedback or real-world experiences would be greatly appreciated.Thanks!​@Reny ​@Dmitri Chilovich ​@divyaprakash 

We have a situation where the final (compiled) .lwr file is available in the system but we lost the individual screens/pictures that were compiled into the .lwr file. Now we need to make changes to some of these screens and I am trying to find a way to unbundle the .lwr file that we have. I have Rocket MX and Automation workbench 10.5.4. and I couldn’t find any documentation on decollecting a .lwr file. Any information related to .lwr files is appreciated