*is my misunderstanding? our shop using ACOPY command/rexx to
download/upload file to/from other platforms and this command is not support
in z/os 1.9. *
**
*Description:* The APPC Application Suite is a set of common applications
originally designed to enhance the value of SNA networks for end users.
Because more full-featured alternative applications exist in modern
integrated SNA/IP networks, z/OS V1R8 is the last release that includes the
APPC Application Suite. As of z/OS V1R9, the APPC Application Suite is no
longer shipped with the product and is not supported. But note that APPC
itself remains an integral part of z/OS Communications Server's SNA
functions, and there are no plans to remove APPC from z/OS.
*Element* *or* *feature:*
Communications Server.
*When* *change* *was* *introduced:*
Removal of the APPC Application
Suite effective with z/OS V1R9
was announced on 8 August 2006 in
the z/OS V1R8 general
availability announcement.
Removal of support did occur in
z/OS V1R9.
*Applies* *to* *migration* *from:*
z/OS V1R8 and z/OS V1R7.
*Timing:*
Before installing z/OS V1R9.
[image: Revision]| *Is* *the* *migration* *action* *required?*
[image: Revision]|
[image: Revision]|
[image: Revision]| Yes, if you have applications
[image: Revision]| that use the APPC Application
[image: Revision]| Suite APIs.
*Target* *system* *hardware*
*requirements:*
None.
*Target* *system* *software*
*requirements:*
None.
*Other* *system* *(coexistence* *or*
*fallback)* *requirements:*
None.
*Restrictions:*
None.
*System* *impacts:*
None.
*Steps* *to* *take:* Remove the following:
1. Any applications that use APPC Application Suite AFTP API macros.
2. Any applications that use APPC Application Suite ANAME API macros.
3. The AFTP client REXX exec.
4. The ACOPY client REXX exec.
5. The AFTP server REXX exec.
6. The transaction program (TP) profile of the AFTP server (AFTPD). This
is the profile that defines AFTPD to MVS/APPC.
7. The APING client REXX exec.
8. The transaction program (TP) profile of the APING server (APINGD).
This is the profile that defines APINGD to MVS/APPC.
9. The ANAME client REXX exec.
10. The transaction program (TP) profile of the ANAME server (ANAMED).
This is the profile that defines ANAMED to MVS/APPC.
11. The A3270 application major node definition from VTAMLST.
12. The initialization files of AFTP programs (AFTP, AFTPD, and ACOPY),
the ANAME server, and the A3270 server.
13. The VSAM data set with the APPC Application Suite messages. This data
set is named VSAM.ASUITE.MMSENU.
Consider the following alternatives to the APPC Application Suite:
- For A3270, consider migrating to TN3270. TN3270 provides a much richer
capability assuming IP connectivity exists between the client and server.
- For APING, use the DISPLAY APING command that has been provided as a
native VTAM command for many years.
- A number of other IBM and vendor products provide SNA file transfer
capability (such as NetView FTP) and can be used to replace AFTP. TCP/IP's
FTP capability is also a good alternative if an IP infrastructure is in
place between the client and server.
On 5/23/08, Chris Mason <[EMAIL PROTECTED]> wrote:
>
> Tommy
>
> I'll let John answer questions directed to him - although there are at
> least
> three replies in this thread - including the one you quote from John -
> which
> state quite clearly that the answer to your questions is a resounding 6
> times "yes" - making allowances - perhaps not always a good idea - for
> lapses
> in grammar and some to be assumed question marks.
>
> An example of making allowances for lapses in grammar is that I assumed in
> my previous post that you were confusing "APPC" and the "APPC Application
> Suite". From the detail you give concerning the "APPC Application Suite",
> it is
> clear you are quite familiar with it. Thus you must really have got the
> idea
> that APPC/MVS[1] was being withdrawn. We in the list interested in this
> topic - in line with what John requests - would be very grateful if you
> could
> explain where on earth you got the idea that APPC/MVS had been withdrawn.
>
> Chris Mason
>
> [1] I have been obliged to specify APPC/MVS, a component of z/OS, rather
> than simply "APPC" which is primarily an architecture and it would be very
> odd
> to continue to support other LU types while stopping support for LU type
> 6.2.
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
> Search the archives at http://bama.ua.edu/archives/ibm-main.html
>
>
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
