TCP/IP Support of ACCOUNT Subcommand

Copied from old SHARE Requirements system SSEWCP00002: Voting Priority=2.2

+4=3 +3=5 +2=5 +1=7 abstain=4 Priority=2.2 (Please ignore where voting=0.0 elsewhere)

TCP/IP specification defines an ACCOUNT subcommand for use by FTP and TELNET servers. This subcommnad was not implemented in the OS/390 environment. Many customers use account fields supplied by batch jobs; TSO; CICS; and other subsystems for chargeback or in determining budget allocations to support funding data center environments. The account information exists in SMF records generated by these subsystems and is subsequently processed by administrative systems to accumulate resource usage (cpu; print; etc.) for various account codes encountered. Exits also exist to ensure that the userid is authorized to use the account code specified. Many userids are authorized to use more than one account code. It is the user's responsibility to ensure the proper account code is being used for the function being performed. TELNET and FTP daemons provide userid and i/o counts; but do not provide an account code. The only mechanism currently usable would be to assign multiple userids to each user currently authorized to use multiple account codes and force them to use a different userid for each function performed. Data Center management needs to be able to measure resource consumption of its customers. This should be able to be accomplished in a consistent manner across the various services offerred by the Data Center; e.g.; batch; CICS; TSO; DB2; and TCP/IP servers - which can not be done today.