000027092 - Does SAE for Mainframe run natively on zOS?

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000027092
Applies ToSecurID Authentication Engine
SAE version 2.3
Rocket Software
zOS
UNIX System Services
USS
IssueDoes SAE for Mainframe run natively on zOS?
SAE version 2.3 has been ported to run on the zOS operating system but it is not clear from documentation if it runs "natively" or requires zOS' UNIX System Services (USS).
Resolution

 RSA SAE for z/OS does require features of USS for the following tasks.

1)     To import tokens from a token artifact files requires a USS filesystem. (functions RSASAInitXMLRead/RSASAReadXMLRec/RSASAExitXMLRead)

2)     To export a software token requires a USS filesystem. (function RSASaeIssueSWToken2)

No other SAE API function requires USS.

Notes

The zOS distribution of SAE allows the developer to install z/OS SMS files and/or z/OS USS files.  

Choosing SMS files makes it easier to develop using tools like TSO for editing, JCL for compiling and binding, and JCL for execution.

Choosing USS files makes it easier to develop using UNIX tools like vi, cc, ld, etc..

Legacy Article IDa52461

Attachments

    Outcomes