Use the CHKPTINT statement to specify the number of records that can be sent between restart markers when transferring files in EBCDIC block mode or EBCDIC compress mode when the file type is SEQ.
- Server
- This setting applies when the server is the sending site (when
the server is processing the RETR command).
The server ignores this setting when file type is not SEQ.
The server ignores this setting when it is retrieving data from a z/OS® UNIX named pipe.
Requirement: Do not specify a nonzero value unless the client supports the checkpoint and restart function.
- Client
- This setting applies when the client is processing the APPEnd,
PUt, and MPUt subcommands. When you have configured RESTGET TRUE
at the FTP client, this setting applies also to the GEt and MGEt subcommands.
For more information about configuring RESTGET, see the locsite subcommand
in the z/OS Communications Server: IP User's Guide and
Commands and RESTGET (FTP client) statement.
The client ignores this setting when file type is not SEQ.
The client ignores this setting when you are transferring data to or from a z/OS UNIX named pipe.
Rule: Do not specify a nonzero value unless the FTP server supports the RESTart command and checkpoint and restart function.
Syntax
.-CHKPTINT 0-------. >>-+------------------+---------------------------------------->< '-CHKPTINT--number-'
Parameters
- number
- Used to determine when a restart marker is transmitted. The marker
is transmitted after the specified number of records are sent.
If the number value is set to 0, checkpointing does not occur and no marker blocks are transmitted. The default is 0.
Examples
To send a restart marker of every 100000 records when the client is the sending site:
CHKPTINT 100000To enable the checkpoint restart function when the server is the sending site, code the following statements in FTP.DATA:
RESTGET TRUECHKPTINT any non-zero valueUsage notes
- Specify a nonzero value to enable checkpointing during a file transfer. When checkpointing is enabled during a file transfer, you can restart a failed file transfer. To restart a failed transfer from the z/OS FTP client, use the restart subcommand. See the restart subcommand information in z/OS Communications Server: IP User's Guide and Commands.
- Client and server must both support the checkpoint/restart function. From the z/OS FTP client, you can enable or disable the client's support after logging in with a locsite subcommand. See z/OS Communications Server: IP User's Guide and Commands for more information.
- The z/OS FTP server allows you to change the value with a SITE CHKPTINT command. If only certain clients support the restart function, you should code CHKPTINT 0 in the server's FTP.DATA and direct the user to use a SITE command to set the server value after logging in. See the SITE command information in z/OS Communications Server: IP User's Guide and Commands for more information.