On Fri, 11 Jun 2010 20:21:56 +0800, ibmnew <[email protected]> wrote:

> Dear
>     Our shop is z/OS 1.11 now .
>     After z/OS was migrated from 1.9 to 1.11,we issued 'TSO OMVS'
>    command.
>   We got the following messages:
>    FSUM2378 The start of the session was not recorded.  The slot
>    (in /etc/utmpx) for this terminal could not be updated, or a
>   new slot for the terminal could not be created.
>   Function = pututxline(), terminal name = '/dev/ttyp0000',
>   program name = '/bin/fomtlinc', errno = 113 (X'00000071'),
>   reason code = 053501B2,
>    message = 'EDC5113I
>    Bad file descriptor.'
>    We could obrowse the utmpx.We also checked the attribution
>   of  utmpx file,
>   the attribution is shown below:
>   Pathname : /BM00/etc/utmpx
>                                        More:     +
>   File type . . . . . . : Regular file
>   Permissions . . . . . : 644 rw-r--r--
>   Access control list . : 0
>   File size . . . . . . : 2288
>   File owner  . . . . . : BPXOINIT(0)
>   Group owner . . . . . : #SYSSTC(80)
>   Last modified . . . . : 2010-06-10 21:42:40
>   Last changed  . . . . : 2010-06-10 21:42:40
>   Last accessed . . . . : 2010-06-11 04:47:19
>   Created . . . . . . . : 2010-02-02 02:39:16
>   Link count  . . . . . : 1
>   Then we issue 'exit' command,we also get error messages below:
>   #exit
>    FSUM2187I The end of the session was not recorded.  The proper
>   location for recording could not be found.+
>    FSUM2188I Function = getutxline(), terminal name = 'ttyp0000',
>   user name = BJSP41, return value = 0
>
>
>  Could you tell me what reason code = 053501B2 means?    Could you help us
to solve this problem?
>
>Any Suggestions are highly appreciated!
>
>

Are you sure the file system pointed to by that path (/etc) mounted R/W?
Seems unlikely, but this is what the error means:

+--------+--------------------------------------------------------¦
¦ 01B2   ¦ JRBrlmNoWriteAccess                                    ¦
¦        ¦                                                        ¦
¦        ¦ Exclusive byte-range locks are only for files open for ¦
¦        ¦ write.                                                 ¦
¦        ¦                                                        ¦
¦        ¦ Action:  To set a write lock on a file, it must be     ¦
¦        ¦ opened with write access. Reissue the request and      ¦
¦        ¦ specify a file descriptor that has write access to the ¦
¦        ¦ file.                                                  ¦
+--------+--------------------------------------------------------¦

--
Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS       
mailto:[email protected]                                          
Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html 
Systems Programming expert at http://expertanswercenter.techtarget.com/

----------------------------------------------------------------------
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

Reply via email to