Modify example JCL in documentation to include job header

[ATorrise]

https://docs.zowe.org/stable/user-guide/install-zowe-pswi-acquire#:~:text=//USSBATCH%20EXEC%20PGM%3DBPXBATCH%0A%20%20%20%20//STDOUT%20DD%20SYSOUT%3D*%0A%20%20%20%20//STDERR%20DD%20SYSOUT%3D*%0A%20%20%20%20//STDPARM%20DD%20*%0A%20%20%20%20sh%20cd%20/yourUSSpaxdirectory/%3B%0A%20%20%20%20pax%20%2Drvf%20yourpaxfilename.ZOSMF.pax.Z%0A%20%20%20%20/*
Describe the solution you'd like
It would be helpful if you guys provided a job card header with clear variables that the user needs to update and change for their systems.

Any bit of text you guys can write so that the user doesn't have to goes a long way for the user when they are embarking on such a long process.

[JoeNemo]

Basic JCL knowledge of what a JOB card is is still a prerequisite for many ZOS tasks. The user must ask at their site for what is a default set of parameters for this JOB card (the first line in the JCL job). Sorry.