Status messages with CPY (was: RPG prototype for C-language FILE *)

On 14-Jan-2016 15:42 -0700, Buck Calabro wrote:

On 1/14/2016 5:08 PM, John Yeung wrote:

On Thu, Jan 14, 2016 at 3:05 PM, tegger wrote:

I forgot about the straight CPY command. Never remember it until
after the fact. As with most IBM copy commands, doesn't it give
some sort of status when it is copying? The idea was to avoid it
all together as the nature of the files being copied and the
management reasoning behind it.

I have no idea what you mean. What "status when it is copying"? I
actually don't know of ANY commands that give a status *while* it
is doing something.

You issue the command, it does the copy. You don't find out
anything until after it's done.

Several 'long running' commands issue *STATUS messages. You can see
this yourself with CPYF:

CALL QCMD /* get to a command line */
CPYF BIGFILE QTEMP/X CRTFILE(*YES) /* use a file with at least 100k
records */

While CPYF is running, you will see a message at the bottom of the
display to the effect of 'Copying member or label aaaaa in file aaaaa
in lllll'. When CPYF completes, the message goes away. There is no
record of this message in the job log.

The visibility of those Status Messages is contingent on the Status Messages (STSMSG) attribute of the job being set /on/. If one were so inclined, they can be turned off or on; e.g. using the Change Job (CHGJOB) command with STSMSG(*NONE) or STSMSG(*NORMAL). The initial job attribute is resolved\established for the job from the initial USER, and the User Options (USROPT) parameter on the User Profile (USRPRF) [see Change Profile (CHGPRF) or Change User Profile (CHGUSRPRF)] allows specification of the special value *STSMSG for allowance, and the SpcVal *NOSTSMSG to disallow.

Re the comment by the OP about the presumed use of Status Messages by the Copy Object (CPY) command: I have never seen\known-of that command ever issuing any. FWiW: In a test of copying all files [although only several] from my home directory into a subdirectory, as a [not very robust] test, performed just moments ago, and I saw no status messages [though I did not review a trace to see if, I think it is ¿QMHSNSTA?, was invoked].