Batch Admin Report fails with 'Unknown command'

Products

• TPX - Session Management

Issue/Introduction

When running a Batch Administration report to list users and profiles, the execution shows several 'Unknown Command' messages:

TPBL0102 12/10/21.344 09:08:59.72 BUILD PANEL: LOGO
 TPBL1000 12/10/21.344 09:09:00.36 EXTRACT GIVING(EXTFILE) PROFILE AND NO SESSIO
 TPBL1012 12/10/21.344 09:09:00.37 REQUIRED PARAMETER LIST MISSING
 TPBL1000 12/10/21.344 09:09:00.37         (PIDXNAME(--------))
 TPBL1011 12/10/21.344 09:09:00.37 UNKNOWN COMMAND
 TPBL1011 12/10/21.344 09:09:00.37 UNKNOWN COMMAND
 TPBL1011 12/10/21.344 09:09:00.37 UNKNOWN COMMAND
 TPBL1011 12/10/21.344 09:09:00.37 UNKNOWN COMMAND
 TPBL1011 12/10/21.344 09:09:00.37 UNKNOWN COMMAND

----

TPBL1010 12/10/21.344 09:09:00.37 VGET     00130001 return code is   16
 TPBL1053 12/10/21.344 09:09:00.37  means variable not appropriate for this record
 TPBL1000 12/10/21.344 09:09:00.37 ' PROFILE STAGE1 OPTION '
 TPBL1011 12/10/21.344 09:09:00.37 UNKNOWN COMMAND
 TPBL1011 12/10/21.344 09:09:00.37 UNKNOWN COMMAND
 TPBL1011 12/10/21.344 09:09:00.37 UNKNOWN COMMAND

The control cards were:

EXTRACT GIVING(EXTFILE) PROFILE AND NO SESSIONS                        
        (PIDXNAME(--------))                                           
SET RTITLE1                                                             
' PROFILE STAGE1 OPTION '                                              
SET RTITLE2                                                            
' =======   ========= '                                                
REPORT GIVING(RPTFILE) USING (EXTFILE)                                 
(( ' &PIDXNAME'  ' &PIDXGRP' ))       

Environment

Release : 5.4

Component : TPX for z/OS

Resolution

The job failed due to Line numbers in the far right columns that should not be there, and we were interrupting them as part of the control statement .

This happened because of how the user was copying JCL into the member from another member.

Once the line numbers on the right were removed (using the UNNUM command)  the Batch Administration JCL executed successfully.